couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From afters <afters.m...@gmail.com>
Subject Re: CouchDB suitable as session store?
Date Fri, 21 Jan 2011 15:18:52 GMT
To be clear: I recommend redis over couchdb. I have no personal experience
with memcached, and have not heard of Kyoto Tycoon until now (thanks,
Benoit!).

On 21 January 2011 17:15, afters <afters.mail@gmail.com> wrote:

> I've also switched from couch to redis for handling sessions: it allows
> setting expiration times, and should also provide lower latency.
>
> Assuming your sessions don't require persistence and that you can spare the
> memory (or is redis not memory-only anymore?), I'd say go with redis.
>
>  a.
>
> On 21 January 2011 17:04, Paul Davis <paul.joseph.davis@gmail.com> wrote:
>
>> On Fri, Jan 21, 2011 at 9:58 AM, He Shiming <heshiming@gmail.com> wrote:
>> > 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?
>> >
>>
>> Or memcached.
>>
>> > Thanks!
>> > --
>> > Best regards,
>> > He Shiming
>> >
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message