I’m testing couchbase with a java application, in the testing i’m observing the following behaviour:
One application server is doing a loop of gets for random couch docs in a long and constant rate of 2.5K requests per second.
while the test run i’ve set a network delay from the application server to one of the couch servers, for one second, at that point i observe an even degradation of ALL gets to ALL couch servers and not only to the specific couch server alone.
is this a normal behaviour of the sdk implementation?
next step i’m going to try and change the retry policy to fail fast, i think it might improve it. will update.
UPDATED: it didn’t help at all.
just so you will have more info about the test:
- 3 couch servers, each have 4 cpu’s and 8 gb memory
- the bucket i tested on is 100mb bucket
- each doc is 10k
- the app server have 8 cpu’s 8GB
- the jvm gets 4gb
- the sdk is started with one socket per server, 8 io threads and 8 computation threads, kv timeout of 2500ms (the default, changing it to 500ms didn’t change the test, increasing it higher also didn’t change anything) , adding more threads or less threads also did not change
will be happy for any input…