: Cassandra instead of memcached
I think the dataset should fit in memory easily. The main purpose of this would
be as a store for an API rate limiting/accounting system. I think ebay guys are
using C* too for the same reason. Initially we were thinking of using Hazelcast
or memcahed. But Hazelcast
I think the dataset should fit in memory easily. The main purpose of this would
be as a store for an API rate limiting/accounting system. I think ebay guys are
using C* too for the same reason. Initially we were thinking of using Hazelcast
or memcahed. But Hazelcast (at least the community editi
If your writing much more data then RAM cassandra will not work as fast as
memcache. Cassandra is not magical, if all of your data fits in memory it
is going to be fast, if most of your data fits in memory it can still be
fast. However if you plan on having much more data then disk you need to
thin
Thanks guys, this is what I was looking for.
@Edward. I definitely like crazy ideas ;), I think the only issue here is that
C* is a disk space hug, so not sure if that would be feasible since free RAM is
not as abundant as disk. BTW, I watched your presentation, are you guys still
using C* as i
http://www.slideshare.net/edwardcapriolo/cassandra-as-memcache
Read at ONE.
READ_REPAIR_CHANCE as low as possible.
Use short TTL and short GC_GRACE.
Make the in memory memtable size as high as possible to avoid flushing and
compacting.
Optionally turn off commit log.
You can use cassandra like
consider disabling durable_writes in the KS config to remove writing to the
commit log. That will speed things up for you. Note that you risk losing data
is cassandra crashes or is not shut down with nodetool drain.
Even if you set the gc_grace to 0, deletes will still need to be committed to
Thanks Ben, that article was actually the reason I started thinking about
removing memcached.
I wanted to see what would be the optimum config to use C* as an in-memory
store.
-- Drew
On Mar 5, 2013, at 2:39 AM, Ben Bromhead wrote:
> Check out
> http://techblog.netflix.com/2012/07/benchmar
Check out
http://techblog.netflix.com/2012/07/benchmarking-high-performance-io-with.html
Netflix used Cassandra with SSDs and were able to drop their memcache layer.
Mind you they were not using it purely as an in memory KV store.
Ben
Instaclustr | www.instaclustr.com | @instaclustr
On 05/03
Hi Guys,
I'm thinking about using Cassandra as an in-memory key/value store instead of
memcached for a new project (just to get rid of a dependency if possible). I
was thinking about setting the replication factor to 1, enabling off-heap
row-cache and setting gc_grace_period to zero for the CF
