I'm not certain the purpose of the gb_trees backend as opposed to ets, although I imagine it might have faster lookups (and slower inserts). The fs_backend uses one file per object, meaning that you will need lots of files open on a live system.
Sean Cribbs <[email protected]> Developer Advocate Basho Technologies, Inc. http://basho.com/ On Aug 29, 2010, at 3:33 AM, Neville Burnell wrote: > Thanks Sean, > > Do riak_kv_gb_trees_backend and riak_kv_fs_backend have particular > strengths/weaknesses? > > Kind Regards > > Neville > When would one use > > On 29 August 2010 01:02, Sean Cribbs <[email protected]> wrote: > Your choice should be dictated by your use-case. In most situations, > "riak_kv_bitcask_backend" (the default) will work for you. It stores data on > disk in a fast (append-only) log-structured file format. If your data is > transient or doesn't need to persist across restarts (and needs to be fast), > try "riak_kv_ets_backend" or "riak_kv_cache_backend"; the latter uses a > global LRU timeout. If you want to use several of the backends in the same > cluster (for different buckets), use the "riak_kv_multi_backend" and > configure each backend separately. > > Sean Cribbs <[email protected]> > Developer Advocate > Basho Technologies, Inc. > http://basho.com/ > > On Aug 28, 2010, at 5:10 AM, Neville Burnell wrote: > >> Hi, >> >> I'm new to riak, and have been busily reading though the wiki, watching the >> videos, and catching up on the mail list, so I will have lots of questions >> over the next few weeks - so sorry <grin> >> >> To begin, I'm curious about the characteristics of the seven backends for >> riak [1] >> >> riak_kv_bitcask_backend - stores data to bitcask >> riak_kv_fs_backend - stores data directly to files in a nested directory >> structure on disk >> riak_kv_ets_backend - stores data in ETS tables (which makes it volatile >> storage, but great for debugging) >> riak_kv_dets_backend - stores data on-disk in DETS tables >> riak_kv_gb_trees_backend - stores data using Erlang gb_trees >> riak_kv_cache_backend - turns a bucket into a memcached-type memory cache, >> and ejects the least recently used objects either when the cache becomes >> full or the object's lease expires >> riak_kv_multi_backend - configure per-bucket backends >> Unfortunately this amount of choice means I need to do my homework to make >> an informed decision ;-) so I'd love any pointers or to hear any advice on >> performance comparisons, best practices, backends for development vs >> deployment etc >> >> Kind Regards >> >> Neville >> >> [1] http://wiki.basho.com/display/RIAK/How+Things+Work#HowThingsWork-Backends >> _______________________________________________ >> riak-users mailing list >> [email protected] >> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > >
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
