Woha, that's news to me ! Thanks ! Seems to be the most straight forward way to work arond this is to use -i option ... Though I suspect the 2.4 kernel, and maybe 2.6, might have ways to bind to specific CPU's ... Something to keep in mind anyways. I'm curious, why pystones / 50 ? My machine is a 4 CPU, do I still use 50 ? Also, my pystones/50 is 156, which, from reading what i could find on the topic, is low (Default Zope is 500, Plone talks about 750). Mind you the server as a whole isn't very busy (Linux's procinfo says 85% idle!) Is this right ? Also, should pystones be run on an idle system ? Does it matter ? Thanks to this, I've now discovered the -O option, which I've already put into use, we'll see if that improves things. Thanks again for the eye opener ... J.F. -----Original Message----- From: Paul Winkler [mailto:pw_lists@slinkp.com] Sent: Thursday, July 31, 2003 5:59 PM To: zope@zope.org Subject: Re: [Zope] Performance requirements and ZEO On Thu, Jul 31, 2003 at 04:23:39PM -0500, BZ wrote:

I think you could easily start with one box and migrate up. If you are planning on a dual, look into Python and SMP. I remember reading it was not great, so what you could do is run two instances (your ZEOs) one on each processor.

That is correct. Read this: http://www.zope.org/Members/glpb/solaris/report_ps -- Paul Winkler http://www.slinkp.com Look! Up in the sky! It's THE TOFU RAT! (random hero from isometric.spaceninja.com) _______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )