<br><br><div><span class="gmail_quote">On 1/18/07, <b class="gmail_sendername"><a href="mailto:glyph@divmod.com">glyph@divmod.com</a></b> <<a href="mailto:glyph@divmod.com">glyph@divmod.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><span class="q">On 01:59 am, <a href="mailto:jarrod@vertigrated.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">jarrod@vertigrated.com</a> wrote:<br><br>>We have LOTS and LOTS of test harness code and profiling code to pinpoint
<br>>where bottlenecks are. We are going to have process a couple of terabytes a<br>>day thru this system. Latency thru the system is a high priority because of<br>>what kind of system it is.<br><br></span>If you do manage to keep Twisted in the loop on this project, please share what strategy you used. It is unfortunately rare that Twisted is itself a really performance-critical component of any system (especially a highly parallel system), so information about optimization is hard to find.
<br></div>
</blockquote></div><br>It isn't really a failing of Twisted, on non-sparc hardware it preforms awesome! The SPARC hardware is the problem, and the T1000 / T2000 we have be benchmarking just doesn't place nice with single threaded CPU bound apps.
<br><br>We are going to try and replace Twisted with Apache 2.2.x and create a module that does raw connection handliing, and go with the threaded mpm and see how that preforms with the same test client harness we are benchmarking with now.
<br><br>