I ran 12 miles on the treadmill yesterday, easily the farthest I’ve gone on the human hamster wheel in one session, let alone without a real rest break.
I knew inevitably I’d have to do a long run on the turbo. Vegas was simply too hot in the mornings for a quality long run outdoors even before the sunrise. And as much as I’d love to, I can’t afford to drive out of town every weekend and run in a cooler, practical high-altitude locale. Even though my current gym has good air conditioning, you can still get hot and humid running on a treadmill for any extended period of time.
This weekend was a good window to try, with a 12 miler scheduled and between planned trips. (Plus, it turns out weather wasn’t great in any potential weekend destinations anyway)
One issue: Gym treadmills are designed to let you run for 60 minutes maximum plus a 5 minute cooldown.
Thankfully, my gym isn’t anywhere close to crowded enough where I need to get out at 60 minutes, so I can restart the machine and keep going. But, to minimize the break (because I want this to be a continuous run, not two 60 minute easy running repeats with a 1+ minute rest), I have to make sure to restart the machine and get it back up to speed as soon as possible once stopped.
I started the morning relaxing with coffee and a croissant, and ate a sandwich at Starbucks right before heading into the gym armed with only my 17 oz water bottle. I made sure to treat the morning more like a pre-race routine because I knew this task was going to demand a lot from me. The longest I’d recently run without a break on the treadmill was 50 minutes, and 12 continuous miles was going to demand a lot more than 50 minutes of running. I’ve gone over how challenging I find running on the turbo for extended time.
I’ve played around with pacing on recent treadmill runs, but made sure to keep a consistent moderate but sustainable pace for this extended run. I’ve also experimented with running without my glasses to minimize distractions, and ran most of this run without mine on this time. I also made sure to sip water on schedule every 10 minutes. How much is a sip? The bottle only ran out after 2 hours of running, that’s how much. I did pick up the pacing at 60 minutes to more of a marathon-pace effort for about 3 minutes, before the shutdown and restart.
I hit stop on the machine, and powered past the slightly dragged out shutdown sequence by jamming the button until the display went completely off, then jammed the go button until the display came up again and showed the starting countdown. Once the machine started I immediately restored my original running pace.
As complex as this sounds, it took about 45-50 seconds. During this time, the belt kept moving as it decelerated to zero, so I still was able to log a tiny bit of distance before it stopped. I did take more than a sip of water as the machine worked to restart. But if this was any sort of rest break, it wasn’t more than a few seconds, akin to stopping to tie your shoes or fidget with fluid at an aid station. I certainly didn’t feel like I was recovering.
Into the 2nd hour, I finally started to truly battle fatigue at around the 80 minute mark. Again, I had the pace set to a more moderate effort and certainly faster than I usually run long outside, so this didn’t surprise me.
At around 100 minutes the lactic feeling was rich in my legs and maintaining my pace was starting to feel too arduous to continue for another 20 minutes. So I went to an old trick I’ve seen coaches recommend: I threw in some pickups, kicking the pace up to threshold/10K pace for 60 seconds. Then I’d pull way back to an easier pace than I was originally doing for about a minute, to get my legs back, before resuming my moderate pace.
I did this surge bit at 1:41-1:43 (38:00-40:00 on the previously restarted display) and it worked like such a charm I wished I had thought to do it sooner. I did it again at 1:51-1:53 (48:00-50:00) with an even faster surge and again it worked great for making the moderate pace feel more do-able. Once I got to 2:03 and the machine once again demanded a cooldown I kicked the pace up to marathon-effort again and made sure I got to 12 miles before shutting everything down at about 2:07.
This was the first long run in a long while where I felt sore after the run, and it’s also the hardest I’ve pushed on a sustained run since… probably since the 2018 Chicago Marathon (even Vancouver 2019 was more of a sustained easy run out of circumstance).
Something I never really did in prior marathon training cycles was steady-pace long runs. All were usually run as easy as necessary to cover the distance and that was it. And while that’s still valuable and I obviously still intend to run long runs like that, I also want to do long runs of 2 hours, possibly more, at a faster moderate pace. This one went remarkably well, and the soreness plus the completion of the entire planned workout as intended tells me this was a significant breakthrough.
Then, after slamming a bottle of Gatorade, I went and did some lower body strength training, which certainly didn’t help with the soreness but felt good to limber up with after the extended running. I left and got a steak burrito before heading home and taking a nap.
Sitting here the following morning with coffee, I’m still sore but it’s more a lingering soreness than an intense soreness. It’s certainly not delayed onset muscle soreness because there was no delay in feeling it following the workout.
I’ll probably ride the spin bike today (we got back together recently) to circulate things a bit, but otherwise take it easy before a big training week next week. The plan’s to train all five weekdays next week before another travel weekend and remote long run. How easy Monday’s training will be depends on how sore I’m feeling tomorrow morning.
