Details
-
Bug
-
Resolution: Duplicate
-
Critical
-
Cheshire-Cat
-
Untriaged
-
1
-
Unknown
-
KV-Engine 2021-March
Description
Observing ~18 to 20% drop in kv_transactions throughput between single collection vs 1000 collections .
http://showfast.sc.couchbase.com/#/timeline/Linux/kv/transaction/Throughput
Comparison tests -
Avg Throughput (trans/sec), Workload T, 4 nodes, Majority_Persist_Active, 12 vCPU, s=1 c=1000, worker_instance=1
vs
Avg Throughput (trans/sec), Workload T, 4 nodes, Majority_Persist_Active, 12 vCPU, s=1 c=1, worker_instance=1
Test
sl no | no of collections | Throughput (trans/sec) | avg cpu | link |
---|---|---|---|---|
1 | 1 | 376 | ~22% | http://perf.jenkins.couchbase.com/job/hercules-txn/1326/ |
2 | 1000 | 330 | ~28% | http://perf.jenkins.couchbase.com/job/hercules-txn/1313/ |
stats comparison
Avg cpu utilization in case of 1000 collections is significantly higher compared to single collection .
java client side cpu comparison
It's known that we have seen about ~6% drop in kv throughput with large number of collections (mostly to sanitize incoming collections in each operation) MB-39594.
However trend seen in case of kv_collections seem to be alarming considering degradation is quite indeterministic across different durability levels .
*I will share consolidated comparison across different durability levels soon .
Attachments
Issue Links
- relates to
-
MB-44933 Control the number of config checks that ns_server runs against memcached
- Closed