Thanks Kevin,
It's a very good architecture option. I'm afraid a bit too late to
test.. I'm already in production with the new architecture and CPU
affinity. It's running smoothly though.. :-)
Regards
Hugo
On 3/22/06, ksmith99 <[EMAIL PROTECTED]> wrote:
>
> Hi Hugo,
>
> I've got a similar setu
Hi Hugo,
I've got a similar setup, Compaq DL580 on a Quad Xeon with 3gb of ram on
Debian.
To overcome the GIL and avoid dealing with CPU affiinity and to optimize
server utilization, I started using Xen virtualization to create multiple
virtual servers. It's open source and works great.
Check o
Hugo Ramos wrote at 2006-3-15 17:45 -0300:
>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
On Thu, Mar 16, 2006 at 02:38:04PM +0100, Stefan H. Holek 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.
On that note, if running linux on a box with IDE disks, make sure
that
Thank you all !! (very insane multiple exclamation marks)
I've been trying different scenarios and Zope performance increased 10
to 11 times faster...
Cheers
Hugo
On 3/16/06, Stefan H. Holek <[EMAIL PROTECTED]> wrote:
> a) Your system may be I/O bound - not CPU bound - so you will ne
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
Why do you want to do this? Do you believe that this is more effective
or efficient than the scheduling algorithm that Linux uses? Binding an
application to a single processor makes very little sense at all.
If Zope really is your limiting factor, then you need to spread that
load over as many pro
You can do something like:
/usr/bin/taskset -c 0 zeo/bin/zeoctl start
/usr/bin/taskset -c 1 zope.a/bin/zopectl start
/usr/bin/taskset -c 2 zope.b/bin/zopectl start
/usr/bin/taskset -c 3 zope.c/bin/zopectl start
You then need to load-balance across the ZOPE instances with (eg Pound or
Squid).
On Wed, Mar 15, 2006 at 05:45:23PM -0300, 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 proc
