<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Odometer stopped working</title>
	<atom:link href="http://www.rumblingedge.com/2006/10/31/odometer-stopped-working/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rumblingedge.com/2006/10/31/odometer-stopped-working/</link>
	<description>Tracking developments in Mozilla Thunderbird builds</description>
	<lastBuildDate>Thu, 09 Sep 2010 02:07:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Daniel M</title>
		<link>http://www.rumblingedge.com/2006/10/31/odometer-stopped-working/comment-page-1/#comment-1137</link>
		<dc:creator>Daniel M</dc:creator>
		<pubDate>Wed, 01 Nov 2006 13:18:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.rumblingedge.com/?p=680#comment-1137</guid>
		<description>One consideration to make on this issue is the use of KeepAlives. You can set in Apaches Environment the amount of simultaneous connections to the server. The more connections the more memory that will be consumed by all process&#039;. One idea might be to set the KeepAlive=Off the downside of this is that users connections will be droppped as soon as their request is filled. This will in turn allow traffic to move across the server faster, but at a cost of performance on larger request.
The second option is to leave KeepAlive=On but limit the KeepAlive time to about 5 seconds. This will increase performance considerably on large page loads but will kill off all unused worker process&#039; after 5 seconds allowing the available worker process&#039; to be freed up much faster.
This is just an idea. In theory it sounds good :)
</description>
		<content:encoded><![CDATA[<p>One consideration to make on this issue is the use of KeepAlives. You can set in Apaches Environment the amount of simultaneous connections to the server. The more connections the more memory that will be consumed by all process&#8217;. One idea might be to set the KeepAlive=Off the downside of this is that users connections will be droppped as soon as their request is filled. This will in turn allow traffic to move across the server faster, but at a cost of performance on larger request.<br />
The second option is to leave KeepAlive=On but limit the KeepAlive time to about 5 seconds. This will increase performance considerably on large page loads but will kill off all unused worker process&#8217; after 5 seconds allowing the available worker process&#8217; to be freed up much faster.<br />
This is just an idea. In theory it sounds good <img src='http://www.rumblingedge.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Bishop</title>
		<link>http://www.rumblingedge.com/2006/10/31/odometer-stopped-working/comment-page-1/#comment-1136</link>
		<dc:creator>Alex Bishop</dc:creator>
		<pubDate>Wed, 01 Nov 2006 01:02:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.rumblingedge.com/?p=680#comment-1136</guid>
		<description>I thought Jason had already contacted you about this. It was disabled because it was the script was using up virtually all of the Apache worker threads. I&#039;ll have a look and see if I can figure out a way to make it work without killing the server.
</description>
		<content:encoded><![CDATA[<p>I thought Jason had already contacted you about this. It was disabled because it was the script was using up virtually all of the Apache worker threads. I&#8217;ll have a look and see if I can figure out a way to make it work without killing the server.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.644 seconds -->
