<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Hungry Machine &#187; stats</title>
	<atom:link href="http://blog.hungrymachine.com/tag/stats/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.hungrymachine.com</link>
	<description>The guys behind LivingSocial</description>
	<lastBuildDate>Sun, 25 Oct 2009 15:08:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Reviewing Application Health with HAProxy Stats</title>
		<link>http://blog.hungrymachine.com/2008/03/27/analyzing-application-performance-with-haproxy-stats/</link>
		<comments>http://blog.hungrymachine.com/2008/03/27/analyzing-application-performance-with-haproxy-stats/#comments</comments>
		<pubDate>Thu, 27 Mar 2008 11:29:00 +0000</pubDate>
		<dc:creator>val</dc:creator>
				<category><![CDATA[All]]></category>
		<category><![CDATA[Ops]]></category>
		<category><![CDATA[Rails]]></category>
		<category><![CDATA[haproxy]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[stats]]></category>

		<guid isPermaLink="false">blog.hungrymachine.com/2008/06/05/analyzing-application-performance-with-haproxy-stats</guid>
		<description><![CDATA[
One of the methods we use for checking the health of our applications is stats collected from HAProxy. We utilize it to see how many requests are scheduled for execution on mongrel instances. The graph is one indication of how our applications perform. When we launched the new version of the site three weeks ago, [...]]]></description>
			<content:encoded><![CDATA[<div>
One of the methods we use for checking the health of <a href="http://www.livingsocial.com/">our applications</a> is stats collected from <a href="http://haproxy.1wt.eu/">HAProxy</a>. We utilize it to see how many requests are scheduled for execution on mongrel instances. The graph is one indication of how our applications perform. When we launched the new version of the site three weeks ago, the graph for a single vertical (ReadingSocial) on a typical Tuesday looked like this:
</div>
<div style="padding-top: 10px;">
<img src="http://blog.hungrymachine.com/assets/2008/3/27/old-hastats.jpg" width="100%" />
</div>
<div style="padding-top: 20px;">
So, between porting all verticals to Myspace, Orkut, Bebo, and enhancing the functionality, we spent some time on optimization. In addition to analyzing slow-query logs with <a href="http://hackmysql.com/mysqlsla">mysqlsla</a>, Aaron wrapped all external API calls (and we do a lot of them &#8211; to Amazon, Facebook, Myspace, etc) in slow monitoring so we could see where the latest external bottleneck was so we could fix it one by one. Three weeks later the graph became much more peaceful:
</div>
<div style="padding: 10px 0;">
<img src="http://blog.hungrymachine.com/assets/2008/3/27/new-hastats.jpg" width="100%" />
</div>
]]></content:encoded>
			<wfw:commentRss>http://blog.hungrymachine.com/2008/03/27/analyzing-application-performance-with-haproxy-stats/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
