Re: [Zope-dev] Zope, forking and cpu-affinity

2004-02-12 Thread Dario Lopez-Kästen
Toby Dickenson wrote:

On Thursday 12 February 2004 08:26, Dario Lopez-Kästen wrote:
that is more than 2 processes for a single instance...
one of them is the supervisor process that restarts the main zope process if 
it crashes.

the others are all threads of one process. one main medusa thread, and 4 
publisher threads.
ah. I see - thanks. Doing some further testing on another machine tells 
me that on RH AS Enterprise 3 (or what's-it's-name), zope is listed as 
only two threads, as expected.

Thank you for the clarification.

Sincerely,
/dario
--
-- ---
Dario Lopez-Kästen, IT Systems & Services Chalmers University of Tech.
___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope, forking and cpu-affinity

2004-02-12 Thread Toby Dickenson
On Thursday 12 February 2004 08:26, Dario Lopez-Kästen wrote:
> Dieter Maurer wrote:
> > Zope itself does not fork (unless you use "system", "popen" or things
> > like that; in these cases, you do not want to bind the children to the
> > same processor).
>
> Well, I had that impression as well, but here is the output of ps on my
> machines (edited for cruft-removal):
>
> UID  PID   PPID  C STIME TIME CMD

> zope 32538 14379 0 Feb09 00:02:32 python2.1 z2.py -X -w 
> zope 32539 32538 0 Feb09 00:00:00 python2.1 z2.py -X -w 
> zope 32541 32539 0 Feb09 00:00:09 python2.1 z2.py -X -w 
> zope 32542 32539 0 Feb09 00:00:11 python2.1 z2.py -X -w 
> zope 32543 32539 0 Feb09 00:01:52 python2.1 z2.py -X -w 
> zope 32544 32539 0 Feb09 00:01:41 python2.1 z2.py -X -w 
>
> that is more than 2 processes for a single instance...

one of them is the supervisor process that restarts the main zope process if 
it crashes.

the others are all threads of one process. one main medusa thread, and 4 
publisher threads.

-- 
Toby Dickenson


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope, forking and cpu-affinity

2004-02-12 Thread Dario Lopez-Kästen
Dieter Maurer wrote:

Zope itself does not fork (unless you use "system", "popen" or things like
that; in these cases, you do not want to bind the children to the same
processor).
Well, I had that impression as well, but here is the output of ps on my 
machines (edited for cruft-removal):

UID  PID   PPID  C STIME TIME CMD
zope 32538 14379 0 Feb09 00:02:32 python2.1 z2.py -X -w 
zope 32539 32538 0 Feb09 00:00:00 python2.1 z2.py -X -w 
zope 32541 32539 0 Feb09 00:00:09 python2.1 z2.py -X -w 
zope 32542 32539 0 Feb09 00:00:11 python2.1 z2.py -X -w 
zope 32543 32539 0 Feb09 00:01:52 python2.1 z2.py -X -w 
zope 32544 32539 0 Feb09 00:01:41 python2.1 z2.py -X -w 
that is more than 2 processes for a single instance...

This is on both RH7.3 and RH AS 2.1...

I don't think these are threads, but I couldn't say for sure (and they 
have different pids). I don't know how tor turn threading off for ps/top.

How can I tell if these are threads or "real" processes?

Thanks,

/dario

--
-- ---
Dario Lopez-Kästen, IT Systems & Services Chalmers University of Tech.
___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope, forking and cpu-affinity

2004-02-11 Thread Dieter Maurer
Dario Lopez-Kästen wrote at 2004-2-11 09:39 +0100:
>I have some trouble doing cpu-afiinity wiht zope. I can affinitise the 
>parent process just fine, however, zope forks and the children get 
>spread out all over the CPUs.

Zope itself does not fork (unless you use "system", "popen" or things like
that; in these cases, you do not want to bind the children to the same
processor).

"z2.py" has an option (on by default on Unix) that uses
a daemon supervising Zope. This daemon forks once
to spawn the real Zope process.

-- 
Dieter

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] Zope, forking and cpu-affinity

2004-02-11 Thread Dario Lopez-Kästen
Hello,

I hope this is not the wrong list...

I have some trouble doing cpu-afiinity wiht zope. I can affinitise the 
parent process just fine, however, zope forks and the children get 
spread out all over the CPUs.

I do not yet wish to resort to shell-hacking the ouput of ps -ef, so I 
was wodering if there are some documents that explain the forking nature 
of zope.

Any help is appreciated.

Sincerely,

/dario

--
-- ---
Dario Lopez-Kästen, IT Systems & Services Chalmers University of Tech.
___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )