Thoughts

Training stacks just turned model development into plumbing

Concurrent multi-LoRA training is turning model development from artisanal experimentation into industrial pipeline management.

Training used to be an event. You’d prepare your data, configure your run, cross your fingers, and wait hours or days to see if it worked. Now it’s becoming a continuous manufacturing process where experiments run in parallel like cars on an assembly line.

The factory floor approach

Concurrent multi-LoRA training stacks are the latest signal that we’re moving from boutique model crafting to industrial production. Instead of spinning up dedicated infrastructure for each experiment, teams are building always-hot engines that can handle multiple training runs simultaneously. Each experiment gets its own LoRA adapter but shares the underlying computational resources.

The efficiency gains are real. Nearly 3x throughput improvements mean the difference between running one experiment per day versus three. But this isn’t just about speed.

When optimisation becomes the product

We’re optimising the optimisation process itself. Training infrastructure is becoming as important as the models it produces. The teams building these stacks aren’t just enabling faster experiments, they’re fundamentally changing how research happens. When you can iterate three times faster, you don’t just get results quicker, you explore different types of problems entirely.

The irony is that as training becomes more efficient, it also becomes more complex. We’ve traded the simple pain of waiting for the sophisticated pain of managing concurrent workloads, shared state, and resource allocation. Progress, but at the cost of turning every ML engineer into a distributed systems expert.