Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of norman.barker@gmail.com
 designates 74.125.83.52 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=WDearh4RHyf8JARcretzDlxVJbvviy00ZMCuOFFzA1pTZA1O/N2qzTpsfnFBwX1bl3
         iwbk9HVdoh7cXOsLREKJ9Ies/ossryhyi1gMTbulAch3gea1jCjQZMgEOXgJhijbSsDX
         IQ2ajlCzwE1inQjt6yMkFWCd+fp0Ig1n8xtdM=
MIME-Version: 1.0
Date: Thu, 17 Jun 2010 16:00:01 -0600
Message-ID: <AANLkTilSznFDQPjj9gqNK1nlub0NF5aBScEVQrf6Wp6-@mail.gmail.com>
Subject: using gzip for db and view indexes
From: Norman Barker <norman.barker@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I am looking at the couchdb db database and view index directory and I
see the files are saved as binary, my indexes and database are getting
fairly large so I tried gzipping them (by hand) and it made a big
difference (at least for my data).

Looking at

http://www.erlang.org/doc/man/file.html

I see that compressed is an option when reading or writing a file, is
it worth trying this out, could it be an option in the ini file so we
could trade off database size versus a possible lag in access?

I can do look into this, does everything go through the couch_file
module and is there a suitable test dataset that we can analyse
performance with?

thanks,

Norman