Conceptual problem with Zope 2.0.1 threads
Hi, I hope someone can enlighten me here. I run a Zope system with 6 threads at the moment. Does this mean that if I get 7 requests to the site, the 7th one has to wait until one of the 6 are through servicing the request? I noticed that when my site went live and got hammered by 50-70 students, that things were slowing down a lot. With our Apache server we have over 200 processes running, and I was wondering about the utility of upping the thread count to a higher (much higher?) number. As an example, can anyone tell me how many threads the main Zope site use? Tone ------ Dr Tony McDonald, FMCC, Networked Learning Environments Project http://nle.ncl.ac.uk/ The Medical School, Newcastle University Tel: +44 191 222 5888 Fingerprint: 3450 876D FA41 B926 D3DD F8C3 F2D0 C3B9 8B38 18A2
On Fri, 8 Oct 1999, Tony McDonald wrote:
Hi, I hope someone can enlighten me here. I run a Zope system with 6 threads at the moment. Does this mean that if I get 7 requests to the site, the 7th one has to wait until one of the 6 are through servicing the request?
I helped built a heavily modified squishdot site that uses 4 threads to serve about 50000 requests a day. the server technology of ZServer (medusa) is different from apache (or at least it used to be). Medusa uses an asynchronous approach, and one thread can service thousands of requests per second. It is actually one (if not the most) efficient server approaches *as long* as each individual request does not consume too much processing power, otherwise all the rest of the requests will hang. For more info on the technology read the various documents from the medusa site at www.nightmare.com. Pavlos
participants (2)
-
Pavlos Christoforou -
Tony McDonald