Training Methods Intermediate

Local Minimum

A spot that's stuck low, even though lower ground exists

Key points
  • A local minimum is a spot that's lower than everything right around it, but not the lowest point overall.
  • Training only ever moves downhill from wherever it currently stands. So stepping into a spot ringed by uphill on every side, it can't get itself back out.
  • While it's stuck there, it's hard to even tell that it's stuck. Uphill in every direction looks exactly the same as "we've arrived."
  • Rerunning from different starting points, adding momentum, or jostling things with slightly different data each time — all of these help escape.
  • In large models, actually getting trapped is rarer than it seems — what shows up far more often is just a stretch that slows to a crawl.
Contents

1The analogy

Picture a yard right after the rain stops. Water always flows to wherever is lower. There's a drain at the edge of the yard, so eventually the water should end up there. But if there's a slight dip halfway along the path, the water stops right there instead. Stand in that spot and look around — front, back, both sides are all uphill. There's nowhere left to go down.

Days later, the puddle is still sitting there. The drain is only a few steps away and sits much lower — doesn't matter. It's not that the water got lazy; it's that it followed the rule "only go downhill" all the way through. Training stalling out at some middling spot is the same puddle.

2In detail

The rule of moving downhill only

Training checks which direction is downhill from where it stands, then moves a little that way, over and over. The upside of this method is that it never needs to know the whole landscape. Since it only has to read the slope right underfoot, it can handle an enormous number of values just fine.

But reading only what's underfoot has a cost. If every direction from the current spot happens to be uphill, movement stops. Whether there's a much deeper valley somewhere beyond isn't information the slope underfoot carries at all. It's the exact same reason the yard's water can't cross the dip and reach the drain.

You can't tell from inside the puddle

The tricky part of this problem is that it's hard to even notice you're trapped. Loss going quiet and refusing to drop further looks identical to training having finished properly. Just looking at the number on screen, "we've arrived" and "we're stuck here" look the same.

So in practice, people watch the absolute score. If loss has gone quiet but the value is much higher than expected, a puddle becomes the suspect. It's an even clearer signal if the same settings, run several times, land at very different final scores — one run much better than the rest. There's no way to judge from a single low spot alone; it takes comparing several.

Ways to get past the puddle

The first is changing the starting point. Generate several different sets of random starting values, run each one, and keep whichever result came out best. It's the same as pouring water at several different spots in the yard and seeing where it ends up.

The second is adding momentum. Carry forward some of the speed built up from the direction already traveled, and a shallow dip gets crossed by momentum alone instead of stopping the motion. It's the same as a rolling marble carrying enough speed to clear a small groove instead of settling into it.

The third is jostling things on purpose. Rather than using all the data at once, split it into chunks — the gradient comes out slightly different every time, and that wobble helps nudge things out of a shallow spot. Starting with a big step size and shrinking it as training goes on chases the same effect.

Large models tell a different story

If there were only two or three values, the yard picture would hold up exactly. But a real model has millions of values to adjust. For a spot in that space to actually be a genuine puddle, every single one of those millions of directions has to be uphill at once. A spot like that turns out to be rarer than it looks.

What shows up far more often is an in-between spot where some directions go up and others go down. In a place like that, the gradient is nearly zero, so progress stalls for a while — but eventually a downhill direction gets found and the model escapes. That's why when training in a large model appears to stop, it's usually not truly trapped forever — it's just slowed down for a stretch.

3More precisely

A local minimum is a point where the loss is greater than or equal to its value at every neighboring direction. The single lowest point across the entire landscape gets its own separate name — the global minimum. The in-between spot mentioned earlier is called a saddle point, named for its shape: lowest along some directions, highest along others.

The comparison breaks down in places too. Looking down at a yard from above, it's obvious at a glance where's genuinely lowest — but the actual loss landscape has millions of directions, with no way to view the whole thing at once. All that's available is the slope underfoot and the scores seen along the way. And dodging a local minimum to land on the very lowest possible spot isn't always a win, either. The lowest point on training data isn't guaranteed to be the best spot on data the model has never seen, so in practice a slightly-less-low but broad, gentle spot is often preferred instead. A yard also only has one puddle to worry about at a time, while a high-dimensional landscape can have countless shallow spots scattered across it, most of them harmless because momentum or a shuffled gradient carries the model straight through.

4Try it yourself

5Common misconceptions

  • It's easy to think training stopping means it's trapped in a local minimum, but actually it's more often just a stretch where the slope went shallow for a while, or the step size shrank too small.

  • It's easy to think finding the lowest possible spot always makes for the best model, but actually the lowest spot on training data doesn't line up with the best spot on data the model hasn't seen.

  • It's easy to think a bigger model means more puddles, but actually the more values there are, the rarer it gets for every single direction to be uphill at once.

7One-line summary

In shortA local minimum is a spot that's lower than its surroundings but not the lowest point overall — training escapes it by changing where it starts, or by adding momentum and jostling to shake it loose.

Spotted an error or have a better analogy? Suggest an edit · Last updated2026-09-02