First thing I would do is stripe your EBS volumes. I've seen blogs that say this helps and blogs that say it's fairly marginal. (You may want to try rackspace cloud as they're local storage is much faster.)
Second, I would start out with N=2 and set W=1 and R=1. That will mirror your data across two of the three nodes and possibly give you stale data on the reads. If you feel you need stronger durability you increase N and W. As far as heap memory, don't use 100% of the available physical ram. Remember, object heap will be smaller than your overall JVM process heap. That should get you started. On Fri, May 28, 2010 at 3:10 AM, Chris Dean <ctd...@sokitomi.com> wrote: > Mark Greene <green...@gmail.com> writes: > > If you give us an objective of the test that will help. Trying to get max > > write throughput? Read throughput? Weak consistency? > > I would like reading to be as fast as I can get. My real-world problem > is write heavy, but the latency requirements are minimal on that side. > If there are any particular config setting that would help with the slow > ec2 IO that would be great to know. > > Cheers, > Chris Dean >
