> If the database is in memory, why write it to bitcask? Seems like a
> simple replay log is what you want in this situation.
Because it's very handy to have KV over persistent copy :)
> Could this be an artifact of the large # of writes + deletes on the
> file system?
Nope. Each point there is 5
On Thu, Dec 15, 2011 at 10:51 AM, Dmitry Groshev wrote:
> I'm using standalone bitcask as a backend for our in-memory database
> (not opensourced yet). I write ~1.5GB of data to it each 5 minutes
> overwriting almost all keys and after that I run a merge as follows:
If the database is in memory,
