You're right! At the moment, I don't have enough users to make that
happen, but I do plan to switch to Redis, as its protocol is compatible
with memcached.
Shahan
On Tue, 15 Sep 2009 22:59:56 -0700, Chris Goffinet
wrote:
> Using memcached as a write-back cache is good, using it solely for
> se
: Wednesday, September 16, 2009 9:00 AM
To: cassandra-user@incubator.apache.org
Subject: Re: random n00b question
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
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,
wrote:
Is there a specific reason to store the session
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
2009/9/15 Chris Goffinet
>
> Do you really expect a user to open up multiple tabs and start clicking
> concurrently? Is the use case for bots? Remember, if you're trying to
> capture a user's activity and think they might open up many windows, I
> wouldn't be saving that into a session in general
On Sep 15, 2009, at 8:09 AM, Mark Robson wrote:
2009/9/15 Jonathan Ellis
We don't currently have any optimizations to provide "lightweight"
session consistency (see #132), but if you do quorum reads + quorum
writes then you are guaranteed to read the most recent write which
should be fine fo
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
2009/9/15 Jonathan Ellis
> We don't currently have any optimizations to provide "lightweight"
> session consistency (see #132), but if you do quorum reads + quorum
> writes then you are guaranteed to read the most recent write which
> should be fine for most apps.
>
Quorum read / write would be
We don't currently have any optimizations to provide "lightweight"
session consistency (see #132), but if you do quorum reads + quorum
writes then you are guaranteed to read the most recent write which
should be fine for most apps.
On Tue, Sep 15, 2009 at 5:30 AM, Eric Bowman wrote:
> Mark Robson
Mark Robson wrote:
2009/9/15 Matt Kydd mailto:m...@storefu.com>>
We need to persist the sessions and associated shopping baskets /
activity summaries somewhere and Cass seems like a good fit, without
the restrictions imposed by SQL there would be less necessity to purge
old sessi
2009/9/15 Matt Kydd
> We need to persist the sessions and associated shopping baskets /
> activity summaries somewhere and Cass seems like a good fit, without
> the restrictions imposed by SQL there would be less necessity to purge
> old sessions.
>
Purging the old sessions in Cassandra would be
We need to persist the sessions and associated shopping baskets /
activity summaries somewhere and Cass seems like a good fit, without
the restrictions imposed by SQL there would be less necessity to purge
old sessions.
I take the point on though and have made a note to do some sanity
checking on
I'd recommend still using Memcached for sessions. The reason is
because Memcached has built in garbage collection of zombie sessions
(via LRU) and Cassandra does not.
--Joe
On Sep 14, 2009, at 5:09 PM, Matt Kydd wrote:
I'm looking at a similar use for Cass - storing sessions and some
denor
I'm looking at a similar use for Cass - storing sessions and some
denormalised data for fast frontend use.
The app will be Rails and was planned to be using Memcache for
partials, but I'm looking at ways I can get those in to Cass too -
eliminating Memcached altogether from the architecture.
MK
On Mon, Sep 14, 2009 at 5:05 AM, Eric Bowman wrote:
> Hi,
>
> I'm just getting started looking at Cassandra, and wondering if is a
> possible fit around the shape of the problem we think we need to solve. :)
>
> In a nutshell, what I'm wondering is whether it would be possible to use
> Cassandra a
Hi,
I'm just getting started looking at Cassandra, and wondering if is a
possible fit around the shape of the problem we think we need to solve. :)
In a nutshell, what I'm wondering is whether it would be possible to use
Cassandra as front-end kind of session database, with commits eventually
(of
16 matches
Mail list logo
