From user-return-12793-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Sun Sep 19 07:43:42 2010 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 66165 invoked from network); 19 Sep 2010 07:43:42 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 19 Sep 2010 07:43:42 -0000 Received: (qmail 45705 invoked by uid 500); 19 Sep 2010 07:43:41 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 45323 invoked by uid 500); 19 Sep 2010 07:43:37 -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 45309 invoked by uid 99); 19 Sep 2010 07:43:36 -0000 Received: from Unknown (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 19 Sep 2010 07:43:36 +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 akat.metin@gmail.com designates 209.85.212.52 as permitted sender) Received: from [209.85.212.52] (HELO mail-vw0-f52.google.com) (209.85.212.52) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 19 Sep 2010 07:43:15 +0000 Received: by vws14 with SMTP id 14so4281460vws.11 for ; Sun, 19 Sep 2010 00:42:54 -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 :content-transfer-encoding; bh=xD0H0yRsiS3GVfcc20SbYoKCM/fMOu/PqNG0n+otBvw=; b=Xm3ncOSudCja+8zlXduCIvAoHvRRFPxDFteZrXBPLpg41K42VNIRbxUhU9693UgUlX ZWX8o5tl+20VFMt256dkwAlnNq/eB8LLqJyTPV0k7CnuzRlYCzrFqwO09M0DvCHTP++G O+5hIIdiXeqxIT3whfVVMz0qoLdhfv2jShe20= 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:content-transfer-encoding; b=oT98rKJQ9hFQfSWrV99Y7BAkduq8TTrbLPW73hpBCA/xTjnHkVwbJBA8rrHi47B4UP 3UGuAY1g10w+5KyU3NBFI2hhKso8rtaB43zoMqrHvP/iN0qPZ7/yIJ+VxupuXmIjmowa VaaJqP2u76Js4y4HfenoEiJnLjV0exCfwB3PE= MIME-Version: 1.0 Received: by 10.220.110.26 with SMTP id l26mr3935921vcp.279.1284882173050; Sun, 19 Sep 2010 00:42:53 -0700 (PDT) Received: by 10.220.203.129 with HTTP; Sun, 19 Sep 2010 00:42:52 -0700 (PDT) In-Reply-To: <79513BE4-3FE0-4395-9D7C-859FDB1DB09C@gmail.com> References: <79513BE4-3FE0-4395-9D7C-859FDB1DB09C@gmail.com> Date: Sun, 19 Sep 2010 10:42:52 +0300 Message-ID: Subject: Re: Which filesystem is best for deploying couchdb and why? From: Metin Akat To: user@couchdb.apache.org Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hmm, then I start thinking that btrfs is really better than ext4, especially if I want to do things like copy the files in order to deploy (fast) another instance with already build view indexes. And would the couchdb files compress well? On Sat, Sep 18, 2010 at 12:23 PM, Wout Mertens wro= te: > Everything except the 4KB blocksize I would say. While ZFS and Btrfs are = very different on-disk, they are both Copy-On-Write filesystems with extent= s, compression and cheap snapshots. I don't know how the 4KB blocksize sett= ings translates onto Btrfs. > > They are both really suited for the append-only workload CouchDB presents= . > > Wout. > > On Sep 18, 2010, at 9:49 , Metin Akat wrote: > >> What part of this blog post is relevant to btrfs? >> >> On Fri, Sep 17, 2010 at 10:22 PM, Chris Anderson wro= te: >>> On Thu, Sep 16, 2010 at 6:22 PM, Tyler Gillies wro= te: >>>> Wow, thanks for the thought out writeup! >>>> >>> >>> here's a blog post http://letsgetdugg.com/2010/06/25/couchdb-on-zfs/ >>> >>>> On Thu, Sep 16, 2010 at 12:47 PM, Randall Leeds wrote: >>>> >>>>> Disclaimer: I'm no file systems expert. >>>>> >>>>> I recommend something with extents otherwise you might take a big >>>>> performance hit while couch deletes old db files after compaction. >>>>> Compression sounds cool as long as you can do it really fast (are >>>>> there setups where this happens in hardware?). >>>>> >>>>> reiserfs: >>>>> According to wikipedia it "still uses the big kernel lock (BKL) =97 a >>>>> global kernel-wide lock" which makes performance on multiple cores >>>>> suffer. >>>>> It's big benefit, as I always understood it, is being able to pack >>>>> smile files together into single blocks. You will likely not have lot= s >>>>> of small files with Couch :-P >>>>> >>>>> xfs: >>>>> Delayed allocation might be a big performance win with a Couch. Since >>>>> outstanding writes are committed together in chunks and then fsync'd >>>>> all together I bet this feature would do good things for Couch >>>>> performance. >>>>> >>>>> ext(3|4) >>>>> I'd recommend ext4 over ext3. Delayed allocation like xfs as well as >>>>> the multiblock allocator should make it much better than ext3. You >>>>> also get extents. >>>>> >>>>> btrfs/zfs: >>>>> Some of the features of each sound interesting, but nothing that >>>>> stands out to me as "great for CouchDB". Snapshots and backups are >>>>> cool, but Couch is doing this for you already in a sense due to the >>>>> way the btree is appended: CouchDB documents are, in a sense, >>>>> copy-on-write. Checksumming is cool if you think it's important for >>>>> your data integrity. If you want snapshots for backup you can always >>>>> use CouchDB replication. >>>>> >>>>> If you run any tests I'd be very, very interested in seeing your resu= lts. >>>>> >>>>> -Randall >>>>> >>>>> On Thu, Sep 16, 2010 at 03:11, Metin Akat wrot= e: >>>>>> I'm sure almost everybody out there is using ext4/3 (including me), >>>>>> but what about filesystems like btrfs, zfs, reiserfs, xfs. Some of >>>>>> them have very appealing feature-sets (like compression for example, >>>>>> and we all know how greedy is couchdb for disk space). >>>>>> And I know that for example btrfs is not yet "recommended for >>>>>> production". But its time is coming. From what I see, Ubuntu 10.10 >>>>>> works flawlessly on btrfs. >>>>>> So I'd be happy if we have some discussion on the topic, instead of >>>>>> "everybody uses ext4, just use it" kind of stuff :). >>>>>> Couchdb was "alpha software" for years, and we all used it in >>>>>> production, so we are not afraid of alpha/beta software, as long as >>>>>> it's good :) >>>>> >>>> >>>> >>>> >>>> -- >>>> http://www.readwriteweb.com/about#tyler >>>> >>>> Ask me anything ! >>>> >>> >>> >>> >>> -- >>> Chris Anderson >>> http://jchrisa.net >>> http://couch.io >>> > >