I’m pleased to report that my AssetsGraphed Ruby on Rails application has been running continuously for over two hundred days now, as the screenshot below taken from my installation of monit shows. Okay, so AssetsGraphed isn’t exactly getting hammered like Facebook, but this level of reliability supports my decision to choose Rails Machine for hosting my Rails applications. Their choice of running Xen-based VPSs on Linux would appear to be a wise one and I know that 37signals themselves are moving in this direction.
The next milestone will be a year’s continuous uptime—let’s hope that posting this isn’t the kiss of death that takes AssetsGraphed offline! Happy New Year everyone.
2003–2024 John Topley
Comments
There are 3 comments on this post. Comments are closed.
Cool.
But how do you make this considering you need to update the software, or handle high volume of traffic?
--
Kevin
I assume this means that it hasn't missed a ping in 201 days? Or that you haven't stopped the Apache process in 201 days? I would be very very surprised if the individual Ruby processes stayed up that long. What's the configuration of the web server (FastCGI, etc.)?
Good questions.
You're right, it means that Apache (and the VPS it's running on) have been up for that long. Apache is using mod_proxy_balancer with a cluster of four Mongrels behind it. The Mongrels are cycled once a day when the logs are rotated. Static assets such as images, CSS files etc. are served directly from Apache so never touch Rails.
Typically, there was a brief outage not long after I posted this entry and the physical server was rebooted!