Here is an updated 2 hour graph of the same "X-Small" 5-node cluster, after having performed all the Linux tuning steps I had missed first time around. Also added ntpd service to all nodes. Looks like slightly better throughput & latency, but a much cleaner graph overall, and it should "burst" much better: https://dl.dropboxusercontent.com/u/22076075/summary-xsmall-bitcask-5nodes-2hr-tuned-vm.png
Here is the same cluster rebooted as "Medium" Azure VMs, same benchmark settings except: 8 workers, shorter duration. Not sure why it has errors, yet: https://dl.dropboxusercontent.com/u/22076075/summary-medium-bitcask-5nodes-30-min.png Anyways- back to work for me!!! :) On Wed, Oct 2, 2013 at 12:14 PM, Alex Rice <[email protected]> wrote: > Hey, something that is impressive about Riak is how well it performs > even on super low end cloud virtualization (unlike for example, > couchbase, which hardly runs at all unless you have quad cores per > each node) > > Having so much fun benchmarking, it's really distracting me from coding! > > the cluster : 5 nodes on Windows Azure cloud > Ubuntu 12.04, Riak 1.2.4 > node are xsmall vm (1 shared cpu core, 768 mb ram) > > The xmall vms are only $15/month and they are not recommended for > "production". but in a 5 node riak cluster, it's really nothing to > scoff at! > > I suspect the main bottleneck is not the cpu or disk, rather I think > it's the each xsmall node is allowed only 5Mbit/sec on the ethernet. > > Here is a basho_bench graph, if anyone feels like viewing it > https://dl.dropboxusercontent.com/u/22076075/summary-xsmall-bitcask-5nodes-20min.png > > note the basho bench was running on a quad core machine on the same > vlan with 5 workers. _______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
