Downtime, or the lack thereof

So far this system (which, I should note, is running an older version of Windows) has been up for a confirmed 4224 hours (176 days).

That's a lower bound: it's based on the sum of the CPU times of the longest-running processes, as provided by Task Manager. (Multiprocessor or multicore systems will need to divide that figure by the number of processors they have; this is a single-processor system, though.) Since I know I've had to restart Firefox (46+ hours) on a number of occasions — every time a new version has been released in the last six months, for instance — I know it's actually been up longer than that. (Possibly much longer: Firefox tends to consistently take up 10-20% of my total CPU time, so I might be justified in multiplying that figure by 1.1-1.25.)

Half of a year is 182.5 days.

This blog, the Edit Posts interface tells me, has had 166 posts made to it since it was started (not counting this one). A post has been made every single day. Since two of those 166 posts were made on the same day (March 15), it's only been around for 165 days.

— and I have just thought to check the event log, and it reads as having been started on the morning of October 11, 2008. So apparently I am on a three-year-old Windows PC, running a version of Windows that is significantly older than that, that has been up for 209 days despite daily active use. If you had asked me this time last year if such a thing were possible, especially with me as the user, I would probably have bet significant amounts of money that it couldn't ever have happened.

Also, I have been rereading old posts, and suddenly desperately want a very good sandwich.