http://avlooks.net/articles/2006/01/31/optimizing-rails en-us 40 Watching and Wondering <p>For web hosts and developers, this is a big issue. If Rails is not managed well, it can become a huge drain on system resources.</p> <p>Here are some <a href="http://weblog.textdrive.com/article/175/rails-optimizing-resource-usage">excellent guidelines</a> to review. We welcome comments!</p> <p><em><span class="caps">NOTE</span>: We suggest putting all of the following in a daily cronjob to keep your ruby runtime environment fresh. In this script you should stop apache and/or lighttpd first, then start them up after the cleanup operations are complete.</em></p> <h3>Get rid of stale dispatch processes</h3> <p>Whether you are running Apache or Lighttpd, dispatch.fcgi processes, once started, don&#8217;t clean themselves up. Therefore it is a good idea when restarting Apache and/or Lighttpd to check for any stale dispatch.fcgi processes, and get rid of them:</p> <pre> ## Kill stale dispatch.fcgi processes killall -9 dispatch.fcgi </pre> <h3>Purge old ruby sessions</h3> <pre> ## Purge Ruby sessions 1 day (24 hours) old and over find /tmp/ -name 'ruby_sess*' -ctime -1|xargs rm -rf </pre> Tue, 31 Jan 2006 18:47:00 -0600 urn:uuid:9176d922edb8ec1b73d1925148eac60a av@avlux.net (Andrew) http://avlooks.net/articles/2006/01/31/optimizing-rails System Admin Ruby on Rails rubyonrails howto sysadmin <p>Thanks Nathaniel. Points well taken!</p> Sun, 26 Feb 2006 01:53:34 -0600 urn:uuid:49f142ab-da6f-470e-804d-452aa850fd6f http://avlooks.net/articles/2006/01/31/optimizing-rails#comment-9 <p>-1 means everything newer than 24 hours.</p> <p>You want&#8230;</p> <p>find /tmp/ -name &#8216;ruby_sess*&#8217; -ctime +1|xargs rm -f</p> <p>Also, you will note that I left out the -r flag. For deleting files, it is definately overkill to do a -r (recursive) delete.</p> Sun, 26 Feb 2006 00:36:33 -0600 urn:uuid:feb4b0a0-caad-48b4-a43a-561e59d6a7b1 http://avlooks.net/articles/2006/01/31/optimizing-rails#comment-8