Now that I'm back home, I should write up a race report from yesterday.
This is my third Twin Cities Marathon, and even still I'm so impressed by the course. The entire 26.2 miles is gorgeous. It's not as fast as Chicago and I think any intelligent pacing strategy has to allow for a modest positive split because of the tough leg from mile 18 or so through mile 22, but the course has great visual variety and is nice the whole way through. Previously, I've stayed at a hotel at the finish line. This time I stayed a couple blocks from the start. Such a luxury to take care of the morning's business in my hotel room and casually stroll outdoors 30 minutes before the gun. The weather was nearly perfect: about 42 at the start, upper-40s at the halfway mark, and low-50s at the finish. Personally, I prefer it a little colder, but that's just personal preference and the actual weather was great by anybody's standards.
My previous PR was 3:50:09, and I thought that was pretty soft -- the last 10K of that race was my fastest leg, and I felt like I had some left in the tank after finishing. Training went well this time, so I decided to go for 3:45 (8:35 pace). I was prepared to back off and readjust if necessary around the 5 or 6 mile mark. As an "A" goal, I thought I might be able to turn it on a bit toward the end and come in a couple of minutes faster. There was a 3:45 pace group, so I lined up them. I have mixed feelings about pacers. I had one very good experience with a pacer several years ago in a tune-up HM, but I've had some bad ones too. More generally, I hate how people feel obliged to glom onto the pacer. Yeah, you have a rabbit to chase, but you're running in traffic the whole time which is tiring and counter-productive. I decided I would just hang back 100 feet or so from the rest of the group. Close enough to watch the balloons, but also out of the pack. This worked out pretty well, except for water stops. The pacer generally blew past them, which is fine with me, but it led to a bunch of people nearly sprinting past me after each one to get right back in the pacer's back pocket. Clearly that was important, because it's not like gradually catching back up over a mile or so is a viable strategy in such a short event.
I do have to give to give some kudos to this particular pacer. I had my Garmin set to an "elapsed time only" screen specifically because I didn't want to obsess over my real-time pace or worry about Garmin distance vs. official USATF distance. Instead, I just went with the timer and a 3:45 pace band. First of all, the pacer absolutely nailed the first 10K -- every mile was within one second of pace. We got to the halfway point about 40 seconds early, which is perfect for this course. He kind of took off around mile 21 or so; I should have finished 30 seconds behind him, but he was actually nowhere in sight as I approached the finish. Again, that's okay though. 3:45 is a BQ for some women, so I have no objection to him getting them in with a cushion.
More importantly, this guy's approach to hills was exactly what I wanted. He slowed down quite a bit on uphills, rode the downhills hard, and made up for any lost time on even ground. This is ideal. Slowing down on uphills -- even effort, not even pace -- isn't losing time. It's investing time. You give a few seconds now, and you get it back with interest during the final stages of the course. I'm always baffled at how many people fly past me on early hills, when they've got 20+ more miles to go. The thing is, it's easy for a pacer to maintain even pace up a hill because this is an easy pace for him. But it torches the people who are trying to run with him and basically sabotages their race. This guy deserves lots of credit for not doing that, and still nailing his splits.
Anyway, my official splits pretty much exactly describe how my race went, so I'll just go with those:
5K: 8:36 pace. Feels stupidly easy, as it should. Why are MP runs so hard and demoralizing in training, but that same pace is so easy on race day? It's unreal how big a difference that taper period makes.
10K: 8:36 pace between. Completely dialed in.
13.1M: 8:26 pace between. We bank a small amount of time during a relatively easy portion of the course. As we should. Still fresh, all things considered.
30K: 8:39 pace between. The segment from about mile 12 to about mile 18 is as easy as the course gets. I always feel like I should bank a little more time here, but I know what's coming, and holding back a bit is probably the right the thing to do. Really I am just following the crowd though. Timer only, not watching my Garmin splits very closely. As we pass into St. Paul, I am getting pretty tired and beat up, and it is clear that any plans to "turn it on" during the last 10K are not going to materialize. Okay otherwise.
21M: 8:37 pace between. There are a couple of unwelcome climbs as you go from Minneapolis to St. Paul. Then you hit Summit Avenue for miles 21 and 22, which are entirely uphill. At this point, I'm reminding myself that this is why I conserved energy earlier in the race, and this is why I did all those mid-week MLRs.
24M: 8:54 pace between. As it happened, I wind up giving back about 50 seconds on Summit Avenue, which is on the very upper end of what I'm okay with. More problematic though was that I can't get back to goal pace after the course leveled out again at the 23 mile marker. This isn't a blow-up or a wheels-coming-off catastrophe. I am just very fatigued and my legs have had just about enough of this. The good news is that even as I'm fading, I'm still passing people right and left, which is fantastically motivating and takes one mind off how bad this hurts. I spend the last several miles doing the "lasso" thing with fellow runners who were having a worse go of it than I was.
Finish: 8:43 pace between. This is as fast as I can go at this point. I keep reminding myself that this is my last marathon and I want to finish strong. The fact is that I am on fumes, but that's how it really ought to be anyway.
My official time is 3:45:30, which I will happily take. Honestly, I could not have squeezed 30 seconds out of the last 10K. Maybe slightly more conservative pacing early on could have gotten me to sub-3:45, but I'm not going to worry about that. My Garmin tells me that I ran 26.45 (normal for this course; you lose a quarter mile very early in downtown Minneapolis under a bridge or something) for an 8:30 "Garmin pace."
I like distance running, and I perversely enjoy much of marathon training, but the actual marathon itself is pretty punishing and I don't enjoy it the way I enjoy HMs, which don't require as much recovery. Both hamstrings and both calves are all messed up right now, and I can tell I won't be running much if at all this week. (We're taking my son on his first college visit this weekend, which scrubs the super-easy 10 miler I would normally look forward to the weekend after a full). Tentatively, I would like to use this training cycle as a springboard for a sub-1:40 spring half, but we'll see.