A few notes:
* +1 for missing RF and CL cassandra stats.
* Using stripped EBS for m1.xlarge is a bad choice, unless they are using
provisioned IOPS. Which they do not say.
* Cassandra JVM settings are *not* standard. It's a low new heap size and a
larger than default heap size.
* "memtable siz
Hi Andy,
things I find odd:
- Replicacount=1 for mongo and couchdb. How is that a realistic benchmark?
I always want at least 2 replicas for my data. Maybe thats just me.
- On the Mongo Config slide they said they disabled journaling. Why do you
disable all safety mechanisms that you would want i
From their wiki: "The replication is an incremental one way process
involving two databases (a source and a destination).
The aim of the replication is that at the end of the process, all active
documents on the source database are also in the destination database and
all documents that were delete
Here is my own experience testing couchdb versus cassandra for an
internal application.
My test wasn't some dummy test case, it was realistic workloads that
is 95% write and 5% read. We insert data in batches to maximize
throughput. The critical thing for my use case was to answer "when
does the s
There are some interesting results in the benchmarks below:
http://www.slideshare.net/renatko/couchbase-performance-benchmarking
Without starting a flame war etc, I'm interested if these results should
be considered "Fair and Balanced" or if the methodology is flawed in some
way ? (for instance i
