The following reply was made to PR mod_proxy/2896; it has been noted by GNATS.

From: Dirk-Willem van Gulik <[EMAIL PROTECTED]>
To: Edison Figueira <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: mod_proxy/2896: Cache very Low
Date: Mon, 24 Aug 1998 15:35:16 +0200 (CEST)

 On 24 Aug 1998, Edison Figueira wrote:
 
 > 
 > >Number:         2896
 > >Category:       mod_proxy
 > >Synopsis:       Cache very Low
 > >Confidential:   no
 > >Severity:       critical
 > >Priority:       medium
 > >Responsible:    apache
 > >State:          open
 > >Class:          support
 > >Submitter-Id:   apache
 > >Arrival-Date:   Mon Aug 24 06:10:00 PDT 1998
 > >Last-Modified:
 > >Originator:     [EMAIL PROTECTED]
 > >Organization:
 > apache
 > >Release:        1.2.6
 > >Environment:
 > Linux RedHat 5.0
 > >Description:
 > The first access for external pages is very low when proxy is active.
 
 Do you mean that the the first well requests are served slowly; i.e. it
 takes quite some time for the pages to come up ? 
 
 If it is just during startup the case, then you might want to
 read the documentation
 on
        http://www.apache.org/docs/mod/mod_proxy.html#startup
 titled
        'Why does Apache start more slowly when using the proxy module?'
 
 If this does not apply, i.e. the webserver is already running, but it is
 just the first cache request; then a second reason might be that apache,
 upon the first cache access, will do a full cleanup check on the entire
 cache, prior to serving. I.e. any stale pages are removed, etc.
 
 This has been fixed in 1.3.x where apache will 'fork' off a separate
 child to do these janitorial chores. Freeing the server to serve the
 proxy request quickly. 
 
 > >How-To-Repeat:
 > .
 > >Fix:
 > 
 > >Audit-Trail:
 > >Unformatted:
 > [In order for any reply to be added to the PR database, ]
 > [you need to include <[EMAIL PROTECTED]> in the Cc line ]
 > [and leave the subject line UNCHANGED.  This is not done]
 > [automatically because of the potential for mail loops. ]
 > [If you do not include this Cc, your reply may be ig-   ]
 > [nored unless you are responding to an explicit request ]
 > [from a developer.                                      ]
 > [Reply only with text; DO NOT SEND ATTACHMENTS!         ]
 > 
 > 
 > 
 > 
 

Reply via email to