And for a very long time that is what I thought.
We have 5 database servers. They are each multisession servers. If a query
on any one of them is taking any time, every zope user is locked up until
that query finishes, despite the server they are accessing.
I don't think it has a single thing to do with the database access, but I
have somehow gotten my zope installation in such a mode that each user
request is served serially and there is zero parallel processing.
It's not like I've seen a lot of zope installations, and I don't know how
they behave. Typically the pages are served so rapidly that this is not a
noticeable behavior, but our user base and databases have grown to the point
that it has become critical.
Thanks for your help.
From: Andreas Jung [mailto:[EMAIL PROTECTED]
Sent: Friday, May 23, 2008 9:19 AM
To: Jon Emmons; firstname.lastname@example.org
Subject: Re: [Zope] Multithreading sessions
--On 23. Mai 2008 08:58:25 -0400 Jon Emmons <[EMAIL PROTECTED]>
> Is this typical Zope behavior?
No, and it is unlikely that Zope is in charge for this behavior.
You might encounter a situation where your database locks a table or
something like that and therefore blocking other requests.
Zope maillist - Zope@zope.org
** No cross posts or HTML encoding! **
(Related lists -