Correlating my sleep time and run fatigue

Frozen Fitbit

Today's run (street): 4.8 miles

Yesterday afternoon I checked my activity progress on the Fitbit only to discover that the readings hadn't changed since morning. The numbers displayed at 5:00 PM were almost the same as they were at 9:30 AM. I took some steps to see if they would record but the numbers didn't change. I connected the Fitbit to my laptop using the USB charging cable and that seemed to jolt it back to life.

I was happy that the device was working again, but disappointed that I wouldn't get "credit" for the steps, miles and flights of stairs that didn't get captured yesterday. I'll watch the display a little more closely, now that I've had that experience. It was working fine this morning and I took it along during my run.

I again recorded my sleep pattern overnight and saw that I'd slept a total of six hours. The good news was that I "only" woke up six times instead of twelve. The Fitbit site assigned me a sleep efficiency rating of 96%, far better than the first time I tracked my sleep cycle.

Perhaps it was a lack of sleep time that factored into the fatigue I felt during today's run. I'd averaged 40 more minutes of actual sleeping time prior to last night. After yesterday's rest day, I expected to feel slightly more energized than normal, but a few minutes into the run I knew something was missing. I set the best pace that I could, determined to cover my distance target of 4 miles.

When I run, I often think about racing and how I'd feel if I was in a race in that moment. I'll often tell myself that I could manage more speed, if needed. Depending on the distance, I can usually muster enough energy to pick up my speed and sustain a better pace. Today I hoped I had enough in the tank to get me through the route I'd planned.

I was determined to get in a full workout and, after making a few loops through my immediate neighborhood, I crossed into neighborhood #2. I had this dual sensation of feeling tired yet ready to cover my distance. There were a few points where I could have cut the run short, but I didn't. In fact I ended up running almost a mile longer than I expected. I was plenty tired by the time I got home and a little puzzled that my heart rate didn't reflect the perceived effort I was experiencing.

Tomorrow I may keep it short, as I'm close to reaching my weekly mileage goal. If my energy returns I may even do some speed work. I'll try to extend my sleep time 40 more minutes and get back to average. I think that contributed greatly to my tiring experience this morning.

Falling short of daily goals

I'd been thinking about taking another rest day this week because I ran Monday through Thursday. This morning I needed to get into the city for some meetings and I figured today would be as good a day to skip a run. I'm tempted to get on the treadmill and do a quick three miles this afternoon, but I'm sticking to my plan.

I only covered 10,000 steps yesterday and fell short of both my daily distance and flight (staircase) goals. I'd hoped that walking in the city would get me close to today's step goal, but I've still got a ways to go. Even though I rested both Sunday and today, I'm still slightly ahead on weekly mileage. I'll target a couple of longer distance runs this weekend and get my Fitbit stats back in line.

Second tier race with a first tier price

Today's run (street): 3.3 miles

I got an email this morning from the organizers of the Long Island Festival of Races urging me to register for the events that will happen in early May. I've run the LI Half Marathon the last couple of years, so I'd consider doing it again. However, registration for that event closes in a week and I don't know if that's enough time for me to decide. I was thinking that the 10K may be fun to do as an alternative. I can always find another half to run later in the year.

When I looked at the Long Island Festival of Races website to register for the 10K, I was both surprised and amused to see that the cost is $37.00, plus a $3.53 convenience fee. What the heck is a convenience fee? Together, it will cost me $40.53 to run a second tier race. I apologize to those who disagree with that viewpoint, but the LI Festival 10K is just not in the same league as some other Long Island 10Ks. For example, The Great Cow Harbor 10K, Long Island's best race, has a registration fee of only $25. And no "convenience fee". I rest my case.

All of this was going through my mind this morning during my run around the neighborhood. The skies had cleared by the time I went out and the temperature had just nudged past 40°. I had plenty of energy, but I still felt a little stiff-legged. I wondered again whether I should have rested more after the race, or at least done some leg stretches. I enjoyed the workout, but never reached the point where my stride felt flexible. 

I'll give it a couple of days before I decide to spend the money for the Long Island 10K. I'll look for other 10K's around that time to see if there's a better choice. I only have a week left to register for this race. Considering the event doesn't happen until May, I don't find that very convenient.

Overnight surprise, courtesy of the Fitbit

Early to bed, early to rise. And rise and rise...

Today's run (treadmill): 3.2 miles

There was no question that I'd run inside today. It poured overnight and throughout the morning, so I headed upstairs to the treadmill after the kids left for school. Every time I use the stairs I think about the fact that the Fitbit is recording that metric. Yesterday I recorded over 14K steps, climbed 28 floors and traveled 7.4 miles. More interesting than that was what I learned about last night's sleep pattern.

The Fitbit has a wristband that holds the device while you sleep, allowing you to record your sleep and wake time. It also records the number of times you woke up during the night. According to the numbers, it took me 12 minutes to fall asleep and my total sleep time was 6 hours and 36 minutes. Now for the surprise: the data said I'd woken up 13 times between the time I put the device into record sleep mode and when I got up for the day. Strangely enough, the readout said I'd had 91% sleep efficiency. Really?

Perhaps we all wake up multiple times during the night and don't realize it. I do recall waking up a few times and looking at the clock before quickly falling back to sleep. The histogram shows that wake patterns seem to be grouped together, so that three or four "wake-ups" could happen in as many minutes. Either way, I didn't come close to sleeping through the night.

Despite the intermittent waking periods, I seem to be getting sufficient rest. Perhaps that speaks to the efficiency rating. Compared to my "pre-retirement" schedule back in January, I'm probably getting at least one hour's more sleep every night. In the days of 3:30 mornings, I used to have to steal naps on the train. With the 7+ hours of bed rest I've been getting overnight, I feel I have good energy throughout the day.

Sixteen staircases on the Bethpage trail

This morning it was full

Today's run (Bethpage State Park): 4.2 miles

The next couple of days look to be windy and wet, so this morning I figured I'd go someplace where I could enjoy the outdoors. Although the warmer weather has melted most of the snow, I didn't want to deal with the muddy trails at Stillwell just yet. I decided to go to Bethpage and hoped that the gates were open.

When I arrived, I saw a large maintenance truck parked in front of the gate and feared that access would be restricted. I then saw that the gates were open, and as I made my way in, I noticed a couple of people running on the path. The trail head was blocked off with a webbed fence and a sign saying "entrance closed."  Like everyone else, I ran around the sign and headed up the hill toward the original trail.

Despite seeing two runners as I drove in, the trail was almost empty. That wasn't a surprise, as it was a Tuesday morning, not the weekend when I usually run there. I liked the quiet but I wasn't loving the run for the first mile. My legs felt leaden and I wondered if I should have taken an extra day's rest after my race.

I started the day with my Fitbit and was curious to see what data it would capture during my workout. After I reached the one mile point, I turned around and headed back in the other direction. I wasn't looking forward to running up the big hill, but at least I'd be doing it while I was relatively fresh. Once I made it to the top, I continued east and reached the entrance to the new section.  I had covered two miles and my legs still felt like they were carrying ankle weights.

Bethpage is hilly and the route is rolling. Most of the time you are either running uphill or down. The first segment of the new trail has a series of hills that are individually short, but collectively challenging. I ran down these hills until I reached three miles, where I turned around and went right back up. Once I got past the worst of it, I noticed that my legs were feeling a little more flexible.

Once I finished my run, I looked at the Fitbit and saw that I'd covered about 7,000 steps and climbed the equivalent of 16 staircases. The activity meter on the Fitbit (a flower) was full to the top. It also captured my distance accurately, along with calories burned. I liked that the Fitbit, unlike the Garmin, is always on and ready to capture activity at any time. But the Garmin provides valuable data that the Fitbit doesn't record, so I'll use them together.

After lunch, my wife and I went to a local park for a walk and I picked up enough steps for me to modify today's goal to 13,500. My wife already has me beat, and I can see it will be hard to keep up with her. But today was a great start.