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 heshiming@gmail.com
 designates 74.125.82.180 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=Gd21ZjU1NKZgdnFo/FbIyHdnXi1R+8CgqNHgVdyz+rZJX+1IHUoVsmqkQY5ptbuQkR
         dnvvbscncWlZ/2NrBHcltEY76exDqFcfJDWq5dVngTRLaMRbzZGLHYqtTa1SebG54K/k
         zuZBlEiRQIsDiPF/AZpw0QUP8Tz+CtKBCd/Bo=
MIME-Version: 1.0
Date: Fri, 21 Jan 2011 22:58:58 +0800
Message-ID: <AANLkTimd-zZ7k+BHPOMRxqGdspd_agx+eqi+FZu+jYzg@mail.gmail.com>
Subject: CouchDB suitable as session store?
From: He Shiming <heshiming@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I've created a beaker extension to use CouchDB as session store
(because my application is already using couchdb under pylons /
python). The beaker library serializes a dict of objects using pickle.
So it's essentially a key (session id) value (serialized content)
pair. My application puts lots of information in sessions. And some of
them are constantly changing during user navigation.

I quickly noticed that a single user can create some 5MB large
documents during like 3 minutes of navigation. After compacting it's
like 20KB. This doesn't look good because it's taking up too much
space and I may need to constantly go to futon to compact it.
Compacting might be slow because of the size.

I was wondering if there's an option for me to compact a particular
document after each time I save?

Or should I just go for redis for session store?

Thanks!
-- 
Best regards,
He Shiming