incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gaurav Sharma <gaurav.gs.sha...@gmail.com>
Subject Re: Replacing Redis
Date Sun, 20 Feb 2011 05:38:33 GMT
Try Jedis or better-still JOhm if you would like to have automatic object
mapping to Redis. You can select a connection pool of your choice even
though we recommend you use Apache Commons Pool.

Cassandra and Redis are very different beasts and work best at their
respective scales. If you just want a simple cache, Redis can do the job -
it is really fast and operations are atomic and with AOF, data-loss window
can be reduced to max transactions occurring in 1 second :)

All that being said, why are you doing an lpush (list-op) on your KV pairs
and not hset (with pipelining if possible)?

Also, try the v2.2 by directly building off of the redis main branch. It is
much faster than v2.0 and Jedis/JOhm are compatible with 2.2


On Fri, Feb 18, 2011 at 12:00 PM, Benson Margulies <bimargulies@gmail.com>wrote:

> typical experiment.
>
> Redis 2.0.4 deployed on my macbook pro.
>
> Saves enabled.
>
> appendfsync off.
>
> vm enabled, 1g max memory.
>
> 72 databases. Each database asked to store 13*N key-value pairs with
> lpush, bucket size not very big, N -> 500,000.
>
> Client jredis.
>
> Start running against a stream of inputs. Sooner or later, client
> times out 'last operation not performed'.
>
> These could be jredis bugs, but I don't care to find out.
>

Mime
View raw message