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:
    case bitcask:needs_merge(BitcaskRef) of
        {true, Files} ->
            bitcask_merge_worker:merge(DataDir, [], Files);
        false ->
            ok
    end.
For now it runs for some days under test load and when I've analyzed
logs I saw something strange. Here
http://img804.imageshack.us/img804/1060/fromlogs.png the upper graph
depicts a durations of merges; as one can see, there at least 2 "saw"
forms with different time scales overlapped. Is there any reason why
it is so? I have a gut feeling that such a variance isn't so good :)

_______________________________________________
riak-users mailing list
[email protected]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Reply via email to