Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 23927 invoked from network); 21 Aug 2007 20:10:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Aug 2007 20:10:46 -0000 Received: (qmail 27299 invoked by uid 500); 21 Aug 2007 20:10:33 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 27198 invoked by uid 500); 21 Aug 2007 20:10:32 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 27187 invoked by uid 99); 21 Aug 2007 20:10:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Aug 2007 13:10:32 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of paul.marsh@gmail.com designates 64.233.182.187 as permitted sender) Received: from [64.233.182.187] (HELO nf-out-0910.google.com) (64.233.182.187) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Aug 2007 20:10:32 +0000 Received: by nf-out-0910.google.com with SMTP id c10so932060nfd for ; Tue, 21 Aug 2007 13:10:11 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=QzsRd0r4oKj/7DFwWjbhdb5d74dBbNbaAZxxzW7VvicWOxNiDL8RXpc2g/qHBGlV3c0FG5WRv0f4ex/QgUWibR2tTwAjdwIgdfyXWTZv+Bj8BnJMVvYhA5f1UxwoJ7eqW5dH69hGc8JpkZqFfTf0ZKnZqn0qm+EN8rBLyHmIUjg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=rnelF71a2nDSR8CBO2rh43dLNMSWxMaXMvx4Dp/pUhFBMBwiM3uL9i6OnaMUq8mfz4RN3qdqWmHP+zoqjVTNVpwqeaMk8KinONX0dvEE27h0PFSU2ncEX2NJMFgy25Yjrzl2xIKO8KKcsnURV6vLYxMCOPhdt8/zJTadWN0/afk= Received: by 10.78.138.6 with SMTP id l6mr3045038hud.1187727010655; Tue, 21 Aug 2007 13:10:10 -0700 (PDT) Received: by 10.78.187.18 with HTTP; Tue, 21 Aug 2007 13:10:10 -0700 (PDT) Message-ID: <63a3d0be0708211310y33c528fdofbb1b4d88c6d2ef1@mail.gmail.com> Date: Tue, 21 Aug 2007 16:10:10 -0400 From: Paul To: users@httpd.apache.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <63a3d0be0708201247r7d263547uf6a102e5deee3180@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] mod_mem_cache & mod_disk_cache Issues Joshua, Thank you for the reply. I'll dig deeper into the list for the disk_cache not storing files for the specified time. I was under the impression that mem_cache would be faster. I had planned on storing files that are accessed many times from a couple of directories, ie, /xml/ or /images/ in memory so they'd just sit there happily. Then for the dynamic parts of the site disk_cache could store those requests. I'll stick with just disk_cache for now. -Paul On 8/21/07, Joshua Slive wrote: > On 8/20/07, Paul wrote: > > All, > > > > I am having a heck of a time with getting mod_cache to work properly. > > I am trying to have it cache a mixture of static files and proxy > > generated content. > > > > I'd greatly appreciate any suggestions. > > > > First with mod_mem_cache I am seeing entries in my logs like the > > following for a URL content generated by a proxy-balancer backend : > > Are you using mem_cache and disk_cache simultaneously? Why? > > I'd recommend focusing on disk_cache, which is better tested and ofter > more performant than mem_cache anyway. > > > Secondly my mod_disk_cache is not storing pages for the amount of time > > specified. I can see that perhaps some requests get sent to the > > backend and before it can reply a second one comes in. > > This issue has been discussed on the dev list at some length. There is > really no easy way to handle it. You don't really want to hold all the > other requests waiting for the first to finish. And if you try to > stream the cached content to the other requests, you wind up in big > trouble if something goes wrong with the first request. > > Joshua. > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See for more info. > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org > " from the digest: users-digest-unsubscribe@httpd.apache.org > For additional commands, e-mail: users-help@httpd.apache.org > > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org