Couchbase CouchbaseConnectionFactoryBuilder configuration for sites with concurrent traffic of around 4000

We are using couchbase server 2.0.0 [Java SDK 1.1.8] for a Rest based web-service. We are supposed to support a benchmark of 4000 concurrent requests.

Right now we are testing with all async-operations for add/get and default ConnectionFactory. We are running into TImeout issues and document corruption.

Is there any documentation or sample configurations for load testing on the Couchbase server? Can somebody show some pointers on how to maximize the performance for Couchbase [with java SDK]?

Could you please give us more information about the topology of your cluster?
The time outs could come from the fact that the server itself cannot reply fast enough.
Also when you say document corruption can you explain?

For me 4000 operation/s should not be an issue with the Java SDK without any special configuration.

Systeminfo on VMware ESXI
RAM - 6 GB
CPU - 4
Redhat - 2.6.32-279.el6.x86_64

Cluster Overview
RAM Overview - Total Allocated (4.84 GB)Total in Cluster (4.84 GB) In Use (30.2 MB) Unused (4.81 GB) Unallocated (0 B)
Disk Overview - Usable Free Space (105 GB)Total Cluster Storage (106 GB) In Use (5.14 MB) Other Data (1078 MB) Free (105 GB)

Adding to this one major pain point is using the CBClient.getView(designDoc, myView). In multithreaded environment within 10-15 concurrent threads it is giving :
Exception in thread “3” java.lang.RuntimeException: Timed out waiting for operation
at com.couchbase.client.internal.HttpFuture.get(
at com.couchbase.client.CouchbaseClient.getView(
at at
Caused by: java.util.concurrent.TimeoutException: Timed out waiting for operation
at com.couchbase.client.internal.HttpFuture.waitForAndCheckOperation(
at com.couchbase.client.internal.HttpFuture.get(
at com.couchbase.client.internal.HttpFuture.get(
… 8 more