Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 77185 invoked from network); 17 Aug 2010 20:11:27 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 17 Aug 2010 20:11:27 -0000 Received: (qmail 36447 invoked by uid 500); 17 Aug 2010 20:11:25 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 36375 invoked by uid 500); 17 Aug 2010 20:11:25 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 36117 invoked by uid 99); 17 Aug 2010 20:11:24 -0000 Received: from Unknown (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Aug 2010 20:11:24 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of randall.leeds@gmail.com designates 209.85.216.180 as permitted sender) Received: from [209.85.216.180] (HELO mail-qy0-f180.google.com) (209.85.216.180) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Aug 2010 20:11:03 +0000 Received: by qyk29 with SMTP id 29so244451qyk.11 for ; Tue, 17 Aug 2010 13:10:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=9bh+wphDa8eWeFyh9lnXvb9KCGTWNsXP1ZOE4i9HRuY=; b=P0oBnilRGqL3ER1Hi1fRBePkJDDzFzYS2yVGt58lAcCzZRN+6b/K0Ew3CGay5DuM2a yEmWslILl7EjBvt9bP6d+M5LLKjJFrurau6G4/wNlPtxgR++ua9Pbp5gzcZyhse40Rrh 4fhyNb2vMDOYmJcUWAdjeN5pPZHQMZde/WoA8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=IvR7k+BTseUtT1HuE9et4+ZyKx3fAOAQYMv281TDxD409VccXy3bzOYMGTv/+QTLcA HaDw2cqwE0KInWH6qGqgMzs9Jo20eqUu1JRmuV8vaDgoIHmsaqqcDP42iGqAZAf/4oO5 U37YcEumUfnQLSsqBZHNvpHgzY/QHg4sc/Qa4= MIME-Version: 1.0 Received: by 10.224.113.27 with SMTP id y27mr4721720qap.67.1282075842282; Tue, 17 Aug 2010 13:10:42 -0700 (PDT) Received: by 10.229.183.78 with HTTP; Tue, 17 Aug 2010 13:10:41 -0700 (PDT) In-Reply-To: <83E56CD6F9BB914AB2CBEDF6038E367005B22D2B@dc1mailbox01.mpls.digitalriver.com> References: <83E56CD6F9BB914AB2CBEDF6038E367005B22D2B@dc1mailbox01.mpls.digitalriver.com> Date: Tue, 17 Aug 2010 13:10:41 -0700 Message-ID: Subject: Re: CouchDb and Web Cache From: Randall Leeds To: user@couchdb.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org Running a cache on the same computer as CouchDB probably won't help much since it will force out the filesystem cache that CouchDB desperately needs to perform really well. If you have another box with spare memory it'll absolutely work as expected if you let it proxy to Couch. On Tue, Aug 17, 2010 at 12:23, Oleg Ryaboy wrote: > Hi, > > > > Does it make any sense to put Web Cache in front of CouchDb? It seems > that while CouchDb provides all of the appropriate headers to make > results cacheable, it has its own cache, so web cache would be totally > superfluous. Is that correct? > > > > Thanks! > > Oleg > >