Glenn and I minutes before the start of the 2014 Portland Marathon. |
Year two of Portland started at 5:10am with a really unwelcome alarm clock. I had some trouble getting to sleep the night before and probably ended up getting 4.5 hours of sleep. Same as last year, and honestly not an issue because I got 9 the night before. After eating a bagel with cream cheese (same as last year) I met Alejandro, Glenn, and Jon to carpool into Portland.
The nerves were out in full force and I kind of felt like throwing up or just not racing. Normal pre-marathon feelings I guess! Anyways, I was in the B corral again, so I settled right behind the 3:25 pacer and waited for the race to start. Glenn was by my side but Alejandro moved up as he was shooting for a sub 3:20. Soon enough the anthem was sung and the race started shortly after 7am. The weather was a pleasant 58F at the time.
MILES 1-6: JUST HOW FAST ARE WE GOING? (7:33, 7:52, 7:52, 7:17, 7:26, 7:42)
This is about mile six. Lookin' good! |
The 3:25 pace group was absolutely, ridiculously fast. I don't know what the fuck they were doing. Normally the Red Lizards, the local group who paces, does a great job. The 3:25 group this year was way too fast. My friend Alejandro finished in 3:22 and they passed him during the final few miles. Seriously? I don't expect perfection, but I expect better than that. The pace groups also have different leaders for the first and second half of the race, so I think that first half group must have been at least five minutes ahead and maybe the second half group actually hit the correct pace.
Needless to say, my race plan was to follow that pace group, it's what my whole plan revolved around. They were supposed to average 7:49/mile. My plan was to follow them though, so I followed. Look at my mile times. Those two 7:52 miles are miles that each have 100 feet of elevation gain. I'm sure their target mile time on those was over eight minutes.
They were fast and I had a suspicion they were fast. The problem was the mile markers were jacked up. Apparently this happened last year too, the Portland Marathon slightly tweaked the course for 2013 but still used the same placement for the mile marker signs in previous years. So my watch said .91 at their "1" marker and pretty soon was consistently two tenths of a mile off.
Between the mile marker confusion and odd pace I thought maybe, just maybe, the pace group knew something I didn't. Anyways, at this point the miles were still coming easy so it wasn't a big deal. Had I a chance to do this again I would pace the entire race by my watch as the 3:25ers were worthless, but you live you learn. The sun was barely up at this point and the weather was still very comfortable.
MILES 7-13: ARE WE THERE YET? (7:34, 7:39, 7:36, 7:44, 7:47, 7:59, 7:46)
Random photo from mile 12. Notice the sun? |
Running was still pretty comfortable though, although it did suck when we hit the turnaround and then had to run two miles back directly into the sunlight. Basically you just had to put your head down and grind along. I think the slipping times here were a result of that sun right in my face. Even though it was probably only 60 degrees, with the sun right in your face it was hot!
By the time I escaped the industrial sun hell portion of the course I had fallen back of the 3:25 pace group by about 30 seconds. I finally made the call that they didn't know what the fuck they were doing and I was going to burn out trying to follow them. That 7:59 mile was a re-adjustment phase in my race that also included some minor uphills in Northwest. If I could hit 7:50-7:55 from here on out I would definitely get my sub 3:30.
MILES 14-18: GRINDING ALONG, UP THE HILL (7:55, 7:52, 8:00, 8:57, 8:12)
Crossing the St. John's Bridge. |
Anyways, by then I had finally dropped them and watched them fade into the distance. I was hitting the mark I needed now and just hoped I didn't burn myself out trying to follow their ill-advised pace for 11 miles. Honestly, in this section I was still feeling pretty good. I didn't know if I would be able to maintain it as it was starting to get warm, but I figured if I could make it up the hill to the St. John's Bridge and still have my legs I'd have a good shot.
I took the hill a lot slower this year because I was very conscious of my too-fast first half and the need not to kill myself up the hill. I ran it in 8:57 (8:34 last year). I remember last year still feeling pretty spry at the top of the hill (didn't last long) but this year I didn't feel that way. I just felt kind of worn down. I still had juice in the legs, but I could feel the race wearing on me. My parents, sister, and aunt were all waiting for me at the end of the bridge. It was awesome to see them and put a pep in my step for a little bit.
MILES 19-24: CRAMPING MY STYLE (8:02, 8:12, 8:24, 8:10, 8:43, 10:01)
It's a little sunny. |
Well, needless to say, when you keep slipping into a new "target pace" every few miles that is getting progressively slower, that is not a good sign. I took a slightly extended walking break through one water station (the 8:24 mile) but otherwise I kept the wheels on the bus going around. Around mile 21 or so I had my first cramp in my left calf. I let out some choice words and slowed down for a bit to make sure it wasn't going to continue.
Another factor in all of this was the heat. This part of the course is very exposed and by this point in the day the sun was up and it was getting hot. By the time I finished it was 70F and at this point it was probably 68F, in my face, and when you are running a marathon that is not comfortable. I would have taken the 55 and drizzly of Vancouver earlier this year because the heat was certainly not helping with my energy level or the cramping.
More exposure evidence. |
Once I hit the bottom of the downhill my legs were basically done. It was amazing how heavy they felt... as soon as the downhill stopped I felt like I weighed 300 pounds! So I was a bit of a shit show for about a mile or so. That 10:01 mile included two different walking breaks and a lot of ugly facial expressions. At one water station I stopped and stretched for a few seconds. Honestly, the fact that mile was only ten minutes is pretty good considering the shape I was in! By the time I hit the mile 24 marker I was running again and wouldn't stop until I crossed the finish.
MILES 25-26.2: SPRINT TO THE FINISH! (9:36, 9:24)
Mile 25! |
Anyways, I was content with my pace and basically told myself that I was going to run this MFer in. By then I had conceded my sub 3:30 was out the window but knew I could still PR. It would be close, but I could PR. If no PR, then a course PR was all but certain. Shuffle along. This part didn't seem as long as it did last year, don't know why, but once I crossed the bridge that last section wasn't too bad. Not that I was enjoying myself, but I think I was content to just shuffle in and finish and knew my body could hold up.
When I got to the "chute" for the final quarter mile or so I was fairly content to just continue to shuffle it in. However, when I turned the final corner and looked at my watch, I noticed it read 3:33:02. I knew my current PR was 3:33:16. I didn't know I had it in me, but I sprinted the final thirty yards or so. I stopped my watch at 3:33:17. Fuck, really? I am pretty conservative with the start/stop so I was hoping for some "official time" relief.
THE AFTERMATH
Finish! A chin for each hour I was running. |
It was great to see them and I also met up with Alejandro, Jon, and Glenn. Alejandro and Jon both slipped off pace during the second half and missed their goals. So while I want to blame my failure on the early 3:25 group pacers, even had I paced myself who knows what would have happened. Here are two very in shape marathoners who both slipped off as well. Glenn, meanwhile, had an awesome race. He slowed a bit toward the end but had a pretty strong race. 3:34 this year after 4:15 last year.
I went out for lunch with my parents and sister. Strangely enough, I wasn't super hungry and really wouldn't be all day. It was nice just to be with them though and I appreciated them all coming out so much. Eventually we limped back to the parking garage and I went home and did absolutely nothing the rest of the day.
I'll have a post with more reflections next. But for now, I'll take the "official time rellief" and the ONE SECOND PR* thank you very much!
Official Chip Time: 3:33:14, 8:08/mile. 520/6258 overall, 402/3050 male, 77/357 M25-29.
* (edit) official time was revised downward one second, meaning it was a 2 second PR.
Even though I knew the outcome, this was so exciting to read! It sounds like that pace group really screwed you over. I think you had a sub 3:30 in the bag with the right pacing. Anyway, I am super impressed as usual. (Your friend Glenn did awesome too. What a huge improvement in just a year!)
ReplyDeleteYeah, I think with appropriate pacing and better weather I could do a 3:28, 3:29, something like that with my current fitness. Oh well, next race!
Delete"A Chin for each hour I was running" made me laugh out loud. I also take extremely flattering race photos. I love getting the ones where I look wrecked. Look how much fun running is! Sucks about the pacer. You expect perfection, but alas, they're humans, too. Assholes. Great job! Proud of you!
ReplyDeleteThanks. Yeah, not sure I want to spend the $25 for a digital copy of that one. I thought it was a very weird place to put your finish line photo person.
DeleteI have to agree, it sounds like the pace group really screwed you. I plan to use a pace group also, after reading this I am going to try and talk to the pacers before the race and if they go out to fast in the first couple miles I am gonna run my own race. I am sure the weather also had something to do with it. Nothing zaps energy like warm weather. At the end of the day you should be proud that you finished and never gave up, to me that's more important than any PR. Also I think the shirtless guy in your "more exposure evidence" needs a little more exposure himself, he's a ghost
ReplyDeleteThe sad part is, he's probably more tan than me! :P Honestly pacers most the time are great and hit the times pretty dead on. This is why yesterday was so surprising and I didn't quite want to believe what was going on. It took me almost half the race to figure that out, so don't make the same mistake! If you watch says they are off, they are probably off!
DeleteInterestingly, the only reason I was able to hit a sub-50 10K last year was because the pacers were running too fast. I planned to follow the 52-minute pacer for as long as I could, and they were going much faster than they should have been. Seeing that pace motivated me to push a little harder, and I ended up passing the 50-minute pacer (something I never even imagined was possible). Of course, a 10K is COMPLETELY different than a marathon ;) But that day, I was grateful that the pacers ran too fast!
Delete