Thank you all !!!!!!!!!! (very insane multiple exclamation marks)
I've been trying different scenarios and Zope performance increased 10
to 11 times faster...
On 3/16/06, Stefan H. Holek <[EMAIL PROTECTED]> wrote:
> a) Your system may be I/O bound - not CPU bound - so you will never
> see the CPU max out because the limiting factors are memory and disk/
> network access.
> b) Make sure to tune Python's checkinterval. While you should
> *always* do that, it is especially important on multi-processor/multi-
> core hardware. The rule of thumb is to run the pystone benchmark,
> divide the "pystones" your machine benchmarks at by 50, and put the
> result into etc/zope.conf.
> python-check-interval 1000
> Once you get the checkinterval right, playing with processor affinity
> becomes a pointless exercise, in my experience.
> c) Always use profiling tools for performance analysis. "Guessing"
> rarely leads to effective optimizations. ZopeProfiler and PTProfiler
> come to mind.
> On 15. Mär 2006, at 21:45, Hugo Ramos wrote:
> > Yellow,
> > I'm using Zope+Apache on a 4 xeon's/4GB ram machine running Debian.
> > I've noticed that the CPU's never go beyond 30% top occupation... but
> > on rush hours the site takes too long to load...
> > I've been reading about process affinity and how it could speed up
> > everything by making zope run on 1 CPU, Apache on another and so on...
> > Has any1 tried this before? Can you point me to some documentation?
> > What's your experience? is it true that not doing this the 4 cpu's
> > will not be 100% used?
> Anything that happens, happens. --Douglas Adams
Hugo Ramos - [EMAIL PROTECTED]
Zope maillist - Zope@zope.org
** No cross posts or HTML encoding! **
(Related lists -