<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Scout ~ The Blog comments on How we handle background jobs</title>
    <link>http://blog.scoutapp.com/</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>Scout ~ The Blog comments</description>
    <item>
      <title>"How we handle background jobs" by derek</title>
      <description>&lt;p&gt;We run background jobs on our Scout servers. Lots of them.&lt;/p&gt;


	&lt;p&gt;As we&amp;#8217;ve grown, they&amp;#8217;ve used dramatically more resources. We needed a way to simmer them down. Most of these jobs load the entire Rails environment &amp;#8211; that&amp;#8217;s a hefty overhead.&lt;/p&gt;


	&lt;p&gt;We&amp;#8217;ve modified how we run background jobs and we&amp;#8217;re seeing great results. If you&amp;#8217;re interested in what we did, &lt;a href="http://napkin.highgroove.com/articles/2008/05/21/running-background-jobs-in-ruby-on-rails-revisited"&gt;checkout Charles&amp;#8217; post on our Highgroove blog&lt;/a&gt;.&lt;/p&gt;


	&lt;p&gt;And finally, here&amp;#8217;s the obligatory semi-promotional graph, generated by Scout, of how the load dramatically decreased after implementation:&lt;/p&gt;


	&lt;p&gt;&lt;img src="http://img.skitch.com/20080522-rdi4iiruxadunkf3cqjpqxa6ex.jpg" alt="Scout ~ Edit Graph"/&gt;&lt;/p&gt;

</description>
      <pubDate>Thu, 22 May 2008 10:24:00 CDT</pubDate>
      <guid>&lt;a href="/articles/2008/05/22/how-we-handle-background-jobs"&gt;How we handle background jobs&lt;/a&gt;</guid>
      <link>&lt;a href="/articles/2008/05/22/how-we-handle-background-jobs"&gt;How we handle background jobs&lt;/a&gt;</link>
    </item>
  </channel>
</rss>
