Leslie Mikesell <[EMAIL PROTECTED]> writes:

> The 'something happens' is the part I don't understand.  On a unix
> server, nothing one httpd process does should affect another
> one's ability to serve up a static file quickly, mod_perl or
> not.  (Well, almost anyway). 

Welcome to the real world however where "something" can and does happen.
Developers accidentally put untuned SQL code in a new page that takes too long
to run. Database backups slow down normal processing. Disks crash slowing down
the RAID array (if you're lucky). Developers include dependencies on services
like mail directly in the web server instead of handling mail asynchronously
and mail servers slow down for no reason at all. etc.

> > The proxy server continues to get up to 20 requests per second
> > for proxied pages, for each request it tries to connect to the mod_perl
> > server. The mod_perl server can now only handle 5 requests per second though.
> > So the proxy server processes quickly end up waiting in the backlog queue. 
> 
> If you are using squid or a caching proxy, those static requests
> would not be passed to the backend most of the time anyway. 

Please reread the analysis more carefully. I explained that. That is
precisely the scenario I'm describing faults in.

-- 
greg

Reply via email to