riak_kv_memory_backend in production
casey at basho.com
Thu Jul 18 14:58:46 EDT 2013
A single node deployment of the memory backend will certainly work,
but will not be as performant as Redis.
Here are some suggestions for running the memory backend in production:
1. Since you are running a single node cluster, set your n_val to 1 
2. Make sure you set the max_memory parameter  to prevent the node
3. In order to get greater concurrency and throughput with the memory
backend, I suggest increasing your ring_creation_size to 128 or 256.
You might need to test which is more performant on your hardware.
4. Turn anti_entropy off. It will just be unnecessary overhead with
5. Make sure your ulimit is raised 
6. Apply our recommended system tunings 
7. You may need to raise some Erlang resource limits in your vm.args file 
On Thu, Jul 18, 2013 at 2:24 PM, kpandey <kumar.pandey at gmail.com> wrote:
> My ultimate goal is to use Riak as that one nosql solution for most of my
> needs like
> 1) In memory immutable data( with guaranteed write and failover so n=3,
> w=quoram, r=1 )
> 2) In memory cache
> 3) bitask with TTL to store immutable session data (n=3, w=quoram, r=1 )
> 4) audit data (n=3, w=1,r=1)
> 5) log data (n=3, w=1,r=1)
> For now I am looking have a 5 node cluster and a test with 5 node cluser.
> View this message in context:
> Sent from the Riak Users mailing list archive at Nabble.com.
> riak-users mailing list
> riak-users at lists.basho.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the riak-users