Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 96293 invoked from network); 12 Oct 2006 03:17:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 12 Oct 2006 03:17:00 -0000 Received: (qmail 62576 invoked by uid 500); 12 Oct 2006 03:16:56 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 62526 invoked by uid 500); 12 Oct 2006 03:16:56 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 62515 invoked by uid 99); 12 Oct 2006 03:16:55 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Oct 2006 20:16:55 -0700 X-ASF-Spam-Status: No, hits=1.4 required=10.0 tests=DNS_FROM_RFC_POST X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [64.236.221.5] (HELO tegmail.turner.com) (64.236.221.5) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Oct 2006 20:16:55 -0700 Received: from cnncimss01.turner.com (CNNCIMSS01.turner.com [10.188.169.201]) by tegmail.turner.com (8.13.6/8.12.11) with ESMTP id k9C3GT0D022856 for ; Wed, 11 Oct 2006 23:16:30 -0400 (EDT) Received: from ATLBH02.turner.com ([10.188.157.232]) by cnncimss01.turner.com with InterScan Messaging Security Suite; Wed, 11 Oct 2006 23:16:29 -0400 Received: from ATLMSG13.turner.com ([10.188.170.53]) by ATLBH02.turner.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 11 Oct 2006 23:15:58 -0400 Received: from 10.188.124.4 ([10.188.124.4]) by ATLMSG13.turner.com ([10.188.170.53]) with Microsoft Exchange Server HTTP-DAV ; Thu, 12 Oct 2006 03:15:57 +0000 User-Agent: Microsoft-Entourage/11.2.5.060620 Date: Wed, 11 Oct 2006 23:16:04 -0400 Subject: Re: httpd 2.2 cache - disable and enable From: "Akins, Brian" To: Message-ID: Thread-Topic: httpd 2.2 cache - disable and enable Thread-Index: AcbtrMAe/s3OP1mfEduqCgANk3aY7g== In-Reply-To: <20061011151130.GA17673@dochas.stdlib.net> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 12 Oct 2006 03:15:58.0313 (UTC) FILETIME=[BCBA6D90:01C6EDAC] X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 10/11/06 11:11 AM, "Colm MacCarthaigh" wrote: somebody have more preferences to one method ? > > I'd be -1 to anything that needed to perform a regular expression test > to check the cache, it'd be a huge CPU hit on something that we're > supposed to be doing as quickly as possible. It's not a very large performance hit to do a regex on almost every request. We do it on some of our sites, as our hacked version of mod_cache allows regex matches. (in fact, all of are matches use the provider mechanism - all providers are "resolved" at config time, not per request). -- Brian Akins Chief Operations Engineer Turner Digital Media Technologies