Using memcached as a write-back cache is good, using it solely for
sessions IMHO is bad idea. Data can be easily pushed out if your
thrashing the more common slabs (unless you really tuned it properly).
On Sep 15, 2009, at 10:56 PM, <[email protected]> <[email protected]>
wrote:
Is there a specific reason to store the session data in the
database? For my web-app, I use a memcached cluster, which
alleviates the database load.
Shahan
On Tue, 15 Sep 2009 10:13:41 -0500, Jonathan Ellis
wrote:
> On Tue, Sep 15, 2009 at 10:09 AM, Mark Robson wrote:
>> Even using quorum reads and writes, if a user in the same session
has two
>> pages active at once, session data would be trashed.
>
> True. But for most web apps I've seen, last-write-wins is just
fine.
> YMMV. :)
>
> -Jonathan
