A question for the audaxers, sports scientists and physiologists out there...
So here's the thing. On rides of up to about 80 miles, my heart rate is relatively high: it bumps along at around 120bpm when I'm cruising,and I feel as if I have lots of power available in my legs so long as I keep the carbs flowing in. However I gradually start to feel tired, and if I don't keep the carbs flowing in then my heart rate goes through the roof with the slightest effort. I can recover this by eating some carbs. For this discussion I'm going to call this 'Type A performance'.
After about 80 miles, my heart rate starts to drop. I feel I've got less power, but I don't notice a marked decline in speed on the flat. I stop feeling hungry, and feel like I could go on all day in a steady way. By about mile 100 my heart rate is way down (sub-100bpm) although my speed hasn't dropped hugely. I'm calling this 'Type B performance'.
I assume that in Type A performance my muscles are firstly then burning through their stored glycogen and then using some metabolic pathway to generate energy where the rate of energy generation is limited by the rate at which my circulatory system can supply something to them (carbs, in some form, presumably). At some point, something runs out and they move to the Type B performance, where my circulatory system can supply whatever it is they need faster than they can use it, so my heart rate drops.
Does anyone know what's going on? It's obviously 'fatigue', but what's happening?
[It's something I've been pondering on for some time, but noticed it really clearly on a ride I did yesterday, and also saw the same effect in the Strava record of @Hankchief's weekend epic in the Cairngorms]