I forgot to mention that 2000 ops/sec was on bitcask, not memory. I didn't bother with the memory backend.
-Jared On Sat, Nov 3, 2012 at 12:05 AM, Jared Morrow <[email protected]> wrote: > Uruka, > > So looking at your results something is really wrong with your setup. I > was surprised by your numbers, so I made two VM's each with only 1gb of RAM > on two different boxes also on a 1gb switch. > > I ran a put of 100,000 keys at 10kb in size. > > I didn't do any tuning at all on the VM's and these were quick Ubuntu > 10.04 VM's with 2 virtual CPU's and 1 gig of ram. I also didn't change any > settings in Riak, except for the IP address and listening ports. > > Here is the summary of the results showing around 2000 ops/sec > https://dl.dropbox.com/u/183971/summary.png > > So my main thought is that you weren't actually using N=1 for your puts > and you were using the default N value of 3, meaning you were writing each > key/value 3 times, and with 2 nodes this is doing a lot of writes to the > same disk multiple times. > > To be sure you have N=1, you can use 'riak attach' on each node and enter > the following command: > > riak_core_bucket:set_bucket(<<"pop1">>,[{n_val,1}]). > > > If you bucket name is "pop1" as in my case. That name is completely > arbitrary. > > Sorry I'm late to this thread, I had to find some time to setup the test. > > For reference I used https://github.com/basho/basho_bench for the > benchmark. With the following .config file > https://gist.github.com/e630b63f4a025a0fb634 > > Hope this helps, > Jared > >
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
