On Sun, 2011-02-20 at 09:04 -0500, Benson Margulies wrote:
> There are two parts to the data footprint, one growing more rapidly
> than the other. The faster growing part has a natural 'redis-friendly'
> data model (keys map to values); but it would map to EHCache as well.
If you're coming into th
Thanks for replying, but it is not at all clear to me that redis was
ever the right solution to the problem at hand. I'm still working out
whether, in fact, Cassandra is.
Up to a fairly large scale, this particular problem needs no 'cache'
at all. It needs a write-behind persistence mechanism -- a
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
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.
Benson,
I was considering using Redis for a specific project. Can you
elaborate a bit on your problem with it? What were the circumstances,
loading factors, etc?
On Fri, Feb 18, 2011 at 9:19 AM, Benson Margulies wrote:
> redis times out at random regardless of what we configure for client
> timeo
redis times out at random regardless of what we configure for client
timeouts; the platform-sensitive binaries are painful for us since we
support many platform; just to name two reasons.
On Fri, Feb 18, 2011 at 10:04 AM, Joshua Partogi wrote:
> Any reason why you want to do that?
>
> On Sat, Feb
Any reason why you want to do that?
On Sat, Feb 19, 2011 at 1:32 AM, Benson Margulies wrote:
> I'm about to launch off on replacing redis with cassandra. I wonder if
> anyone else has ever been there and done that.
>
--
http://twitter.com/jpartogi
