Also, concerning multi-cpu, I think it's the other way around.

Because python processes only use one CPU, it's useless to run one Zope
instance on a multi-cpu system, as only one CPU will be used.  That's why on
multi-cpu system lots of people run at least Zeo + one instance of Zope (and
often one Zope instance per CPU).

But Zeo is really lightweight, so it's worth trying to use Zeo+Zope on a
single cpu system, to take advantage of what Chris describes below.


-----Original Message-----
Chris McDonough
Sent: 14 June 2005 10:46
To: gabor
Subject: Re: [Zope] ZEO recommended for single-cpu?

Typically it's because:

- Zope starts faster in a ZEO setup.
- You can use "zopectl debug" to get into a debugger session
  without shutting down Zope first if you use ZEO.

- C

On Tue, 2005-06-14 at 11:03 +0200, gabor wrote:
> hi,
> i understand that you need to use ZEO when running ZOPE on a multi-cpu 
> machine (or when you want to cluster ZOPE).
> but from mails on this forum it seems that people are also using ZEO 
> when they're running ZOPE on a single-cpu machine.
> why?
> gabor
> _______________________________________________
> Zope maillist  -
> **   No cross posts or HTML encoding!  **
> (Related lists - 
> )

Zope maillist  -
**   No cross posts or HTML encoding!  **
(Related lists - )

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

Zope maillist  -
**   No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to