I think rebooting is pretty important in a computer's life, be it a laptop, desktop or server.

I shutdown my dekstop everyday to save polar bears, and turn it back on in the morning when I use it.
For my servers, I reboot for each OpenBSD upgrade at least, and every now and then, just to make sure that everything comes back up as expected.

This last point is very important to me, especially in the era of auto-configured servers, micro-services shit and similar stuff. Rebooting your service makes sure that it is configured in a reliable and reproducible state.
When your server boots, it MUST be able to reach 100% of it's usability without any manual intervention. If it does not, it means you have a configuration problem.
When I perform "reboot tests" on my servers, I tend to reboot multiple times in a row, to make sure I'm always in a good shape and everything goes in a pretty deterministic way.

Of course, I find huge uptimes to be sexy. I used to value that a lot!
But as time goes by, I realized that my fear of rebooting was growing exponentially to the uptime.

Big uptimes used to be a proof of reliability, in a time were services were bound to the servers they were running on. Nowadays, it's fairly easy to keep a box up and running for years. All you have to do is waiting.

I think that today's true goal is to reach 99.9999% service uptime with servers rebooting every hour.

Now, all this said, the facts:


Note: the above speech was mostly to justify my ridiculous uptimes :P