Comments on: AssetsGraphed Hits 200 Days Uptime http://www.johntopley.com/2007/12/28/assetsgraphed-hits-200-days-uptime/ Sun, 12 Oct 2008 23:28:43 +0000 http://wordpress.org/?v=2.1.2 By: kevin http://www.johntopley.com/2007/12/28/assetsgraphed-hits-200-days-uptime/#comment-16202 kevin Sun, 06 Jan 2008 12:32:57 +0000 http://www.johntopley.com/2007/12/28/assetsgraphed-hits-200-days-uptime/#comment-16202 Cool. But how do you make this considering you need to update the software, or handle high volume of traffic? -- Kevin Cool.
But how do you make this considering you need to update the software, or handle high volume of traffic?

–
Kevin

]]> By: Paul Brown http://www.johntopley.com/2007/12/28/assetsgraphed-hits-200-days-uptime/#comment-18139 Paul Brown Fri, 25 Jan 2008 06:47:26 +0000 http://www.johntopley.com/2007/12/28/assetsgraphed-hits-200-days-uptime/#comment-18139 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.)? 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.)?

]]> By: John Topley http://www.johntopley.com/2007/12/28/assetsgraphed-hits-200-days-uptime/#comment-18152 John Topley Fri, 25 Jan 2008 09:01:03 +0000 http://www.johntopley.com/2007/12/28/assetsgraphed-hits-200-days-uptime/#comment-18152 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 <a href="http://mongrel.rubyforge.org/" rel="nofollow">Mongrels</a> 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! 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!

]]>