> I'm finding that once a user requests a page which runs a
particularly slow sql (say up to 5 minutes),
> any other subsequent requests seem to take the hit as well, and
return very slowly.
Take a look at DadlockDebugger product - you'll see what is happening
with your Zope threads.
Isn't it better idea to execute long running query outside of zope -
external method or sth,
and only check for results even with simple page reload? We did
something like this with pdf
generation and this worked as expected, but of course you need some
additional work to
create such thing.
> So is this blocking effect just expected behavior for zope?
We are using Zope and Oracle too, and even 10 threads... and I didn't
like this. What is your processor doing then? What is the CPU(s?) load.
Zope maillist - Zope@zope.org
** No cross posts or HTML encoding! **
(Related lists -