Bitcask keeps a keymap in ram. That is why it is limited to a certain number of keys in practice. LevelDB does not have these restrictions. Use LevelDB and your main limitation will be disk.
-Alexander Sicular @siculars On Sep 28, 2012, at 11:20 AM, Ingo Rockel wrote: > Hi, > > we are currently evaluating using riak as storage backend for our users > messages (currently running on MySQL). > > This will result to about 4.2 billion k/v with an estimated key-length of > about 25-30 bytes and about average 400 bytes of data (the messages are > usually very short). The amount of data will raise about 8 million k/v per > day. Most data will only be read a few times and never again afterwards. > > I entered this into the bitcask calculator, which resulted in a quite high > number of suggested nodes just because of the memory requirement for storing > all the keys. Is this really necessary if only very little of this data is > really "active"? > > Or should I use Level-DB instead? How do I estimate the amount of nodes with > Level-DB? > > Ingo > > -- > Software Architect > > Blue Lion mobile GmbH > > [email protected] > >>> qeep: Hefferwolf > > www.bluelionmobile.com > www.qeep.net > > _______________________________________________ > 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
