Does more running volume keep paying off?
In 12,233 Polar users before a marathon, more distance went with a faster modelled aerobic speed, saturating weakly; endurance plateaued, then dipped, at the highest loads. Association only.
Emig (Université Paris-Saclay) and Peltonen (Polar Electro Oy) took Polar Flow data from runners who logged a run over the marathon distance between July 2015 and December 2018 with the same GPS watch (Polar V800).
For each runner and marathon they defined a season as the 180 days before it, took the fastest efforts over 5 km, 10 km, half marathon and marathon in that window, and fitted the authors' previously published running model, which describes performance with two indices: vm, the crossover speed associated with maximal aerobic power (MAP), and an endurance index El describing how slowly the sustainable fraction of MAP falls with duration.
The model reproduced race times with a mean error of 2.0% in seasons with three or more efforts. The training analysis used 21,605 seasons from 12,233 runners with at least 30 runs (1,616,004 runs, about 20 million km). Season distance went with a higher vm, on average linearly, with a weak saturation trend at the largest distances.
Faster runners ran their training at a lower fraction of their vm (vm fell linearly with mean relative training intensity between 50% and about 90% of vm); a runner with vm = 4 m/s typically trained at 64-84% of vm, one with vm = 5 m/s up to 66%, so both ran most runs no faster than about 5 min/km.
The endurance index rose linearly with season TRIMP, plateaued around El = 7.5 ± 2 at TRIMP ~25,000, and then showed a statistically significant drop, which the authors suggest may reflect overtraining. The authors stress that cause and effect cannot be separated: fitter runners may simply train more.
Our reading: a large, consistent association that fits the base's observational volume–speed findings (REF-197, REF-090, REF-1004) and adds a visible ceiling at very high loads; it is not a trial and gives no individual dose.
Protocol
Key Results
| Relation or measure | Result | Source |
|---|---|---|
| Model accuracy, seasons with ≥3 efforts (N = 12,309) | mean error 2.0% between predicted and actual race time | text |
| Marathon predicted from shorter efforts only | overall accuracy better than 10% in the most likely parameter range; fastest group (< 160 min) error typically under ±2.5% | text, Fig. 4 |
| vm distribution | approximately normal, mean 4.4 m/s; 1-h utilisation peaks at about 82% of MAP | Fig. 2 |
| vm vs season training distance | rises on average linearly, with a weak saturation trend at the largest distances | Fig. 5a (no slope or CI given) |
| vm vs mean relative training intensity | falls linearly between 50% and about 90% of vm: faster runners train at a lower fraction of vm | Fig. 5b |
| Typical training range | vm = 4 m/s: 64-84% of vm; vm = 5 m/s: up to 66% of vm (about 5 min/km upper pace for both) | text |
| Endurance index vs season TRIMP | linear rise, plateau around El = 7.5 ± 2 at TRIMP ~25,000, then a statistically significant drop | Fig. 5c (test not named) |
| Endurance index vs relative training intensity | exponential rise, matching TRIMP's lactate-based weighting | Fig. 5d |
Mechanisms
Practical Application
Limitations
How this entry was checked and changed
a very large observational dataset (n = 12233 runners in the training analysis), which the rubric would place at B+, held one step lower: training and performance come from the same 180-day window, so the relations are associations whose direction the authors call open; the performance indices are parameters of the authors' own model fitted to self-recorded best efforts that could not be verified as races, not laboratory measures (a model-based criterion costs a grade under the base's rule); the volume relations are given as figures without effect sizes or confidence intervals; and the second author's printed affiliation is the platform's maker, Polar Electro Oy. Read from the full text (open access, CC BY 4.0)