The leveldb back end is not as fast as the default (bitcask), but leveldb does not keep all keys in memory. So for a very large or unbounded set of keys leveldb is superior. Leveldb stores values sorted by key, which also lets riak speed up certain operations such as listing keys in a bucket.
Kresten On 30/03/2012, at 18.17, "idmartin" <idmcr...@gmail.com> wrote: > Is there anyway to analyze Riak objectes to make sure there isnt duplicates > or near duplicates? > > also, > > I want to switch to riak_kv_eleveldb_backend for secondary indexes, was > wondering if there is any disadvantages to this backend? > > Thx > > > -- > View this message in context: > http://riak-users.197444.n3.nabble.com/Riak-Duplicates-storage-backend-tp3871293p3871293.html > Sent from the Riak Users mailing list archive at Nabble.com. > > _______________________________________________ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com _______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
