You'll be constrained in the number of keys that you can store (using the bitcask backend). There's a good spreadsheet for capacity planning: https://spreadsheets.google.com/ccc?key=0Ak4OBkABJPsxdEowYXc2akxnYU9xNkJmbmZscnhaTFE&hl=en&authkey=CMHw8tYO
I don't know how well Riak would behave otherwise in an environment that tight. I'd think you'd be limited to single key lookups, but I have been wrong before. -- Jeremiah Peschka Microsoft SQL Server MVP MCITP: Database Developer, DBA On Tuesday, February 15, 2011 at 4:34 PM, Matthias-Christian Ott wrote: > Hi, > > does somebody have some figures on Riak memory usage? I consider using > it in a highly memory constrained environment (< 32 MiB), but I'm not > sure whether Riak can handle low workloads under such tight constrains > (it consumed > 20 MiB idle). Performance is not relevant to me, I just > need partition tolerance, availability and persistence. > > Regards, > Matthias-Christian > > _______________________________________________ > 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
