NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter



CouchDB: Measuring Read Request Throughput

I am trying to measure max couch throughput - for these tests im happy with just repeatedly requesting the same document. I have some reasonable boxes to perform these tests - they have dual quad core X5550 CPUs with HyperThreading enabled and 24GB RAM. These boxes have a stock install of oracle enterprise linux 5 on them (which is pretty much RHEL5). The oracle supplied erlang version is R12B5 and I am using couch 1.0.1 built from source.

The database is pretty small (just under 100K docs) and I am querying a view that includes some other docs (the request contains include_docs=true) and using jmeter on another identical box to generate the traffic. The total amount of data returned from the request is 1467 bytes. For all of my tests I capture system state using sadc and there is nothing else happening on these boxes

Leave aside for a moment the numbers and read how he is building the test: clear scenario and objectives, clear setup, lots of details about the setup, then experiment, tweak, repeat.

Original title and link: CouchDB: Measuring Read Request Throughput (NoSQL databases © myNoSQL)