News for hackers. Stuff that matters.
Re:Ask HN: Which persistent in-memory database to use? by evgen on Tuesday May 26, 2009 @01:14PM (#627018)
The only thing that really matters here is the write load and the distribution of your reads. The read load can easily be handled by a memecache-like cacheing layer unless it is completely random and you don't have enough RAM. The write load will determine how fast keys get expired out of the cache layer (plus the associated read load this creates) and what sort of i/o throughput your persistence engine will require.

To be completely honest, if memcache, memcachedb, redis, and tokyo cabinet are not getting the job done then you are probably doing things very, very wrong...

Re:Ask HN: Which persistent in-memory database to use? by paraschopra on Tuesday May 26, 2009 @11:48PM (#627953)
>To be completely honest, if memcache, memcachedb, redis, and tokyo cabinet are not getting the job done then you are probably doing things very, very wrong...

I am not saying that they are not getting the job done. They would get the job done but with significant code changes. I was just exploring if there was a better alternative. If I don't find one, I would resort to memcache most probably.