<?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: Multi-Process TurboGears deployments</title>
	<atom:link href="http://compoundthinking.com/blog/index.php/2008/01/21/multi-process-turbogears-deployments/feed/" rel="self" type="application/rss+xml" />
	<link>http://compoundthinking.com/blog/index.php/2008/01/21/multi-process-turbogears-deployments/</link>
	<description>Thinking about programming in new ways</description>
	<lastBuildDate>Tue, 15 Mar 2011 02:30:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Mark Ramm</title>
		<link>http://compoundthinking.com/blog/index.php/2008/01/21/multi-process-turbogears-deployments/#comment-250192</link>
		<dc:creator>Mark Ramm</dc:creator>
		<pubDate>Wed, 15 Oct 2008 18:52:39 +0000</pubDate>
		<guid isPermaLink="false">http://compoundthinking.com/blog/index.php/2008/01/21/multi-process-turbogears-deployments/#comment-250192</guid>
		<description>Jesper, 

I don&#039;t know the exact reason why either.  And it could be specific to the applications I happened to test, all I can say is that 4 processes per processor worked out best for us. 

Perhaps 1 process with 40 threads would have worked just as well, as a recent test showed 50 threads and 1 process per processor working well on a TG2 app that I was testing -- and I don&#039;t think we spent much time playing with the cherrypy thread-count in those earlier tests.</description>
		<content:encoded><![CDATA[<p>Jesper, </p>
<p>I don&#8217;t know the exact reason why either.  And it could be specific to the applications I happened to test, all I can say is that 4 processes per processor worked out best for us. </p>
<p>Perhaps 1 process with 40 threads would have worked just as well, as a recent test showed 50 threads and 1 process per processor working well on a TG2 app that I was testing &#8212; and I don&#8217;t think we spent much time playing with the cherrypy thread-count in those earlier tests.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesper</title>
		<link>http://compoundthinking.com/blog/index.php/2008/01/21/multi-process-turbogears-deployments/#comment-250014</link>
		<dc:creator>Jesper</dc:creator>
		<pubDate>Wed, 15 Oct 2008 10:27:50 +0000</pubDate>
		<guid isPermaLink="false">http://compoundthinking.com/blog/index.php/2008/01/21/multi-process-turbogears-deployments/#comment-250014</guid>
		<description>Hi Mark,

Thanks for your blog post. I am not sure I understand why you would need several processes on each CPU (unless it is a multi core cpu). I would naively expect that the optimal setting is about one process (with multiple threads) per core. Why is this not the case?

Best regards,
Jesper</description>
		<content:encoded><![CDATA[<p>Hi Mark,</p>
<p>Thanks for your blog post. I am not sure I understand why you would need several processes on each CPU (unless it is a multi core cpu). I would naively expect that the optimal setting is about one process (with multiple threads) per core. Why is this not the case?</p>
<p>Best regards,<br />
Jesper</p>
]]></content:encoded>
	</item>
</channel>
</rss>

