Details
-
Bug
-
Resolution: Fixed
-
Major
-
Cheshire-Cat
-
Untriaged
-
Centos 64-bit
-
1
-
Unknown
-
KV-Engine 2021-March
Description
Max ops/sec, cbc-pillowfight, 2 nodes, 80/20 R/W, 512B JSON items, 1K batch size, TLS
http://showfast.sc.couchbase.com/#/timeline/Linux/kv/max_ops/all
4548 - http://perf.jenkins.couchbase.com/job/ares/19963/ - 2791310
4547 - http://perf.jenkins.couchbase.com/job/ares/19966/ - 2799090 <----
4546 - http://perf.jenkins.couchbase.com/job/ares/19967/ - 3719360
4545 - http://perf.jenkins.couchbase.com/job/ares/19964/ - 3762391
Looks like CPU utilization reaches max at 80% and remains at 80% for longer, implying more compute per op. The likely place this was introduced is: https://github.com/couchbase/kv_engine/commit/91d33a7b34791b073577ee882728154128bb3b16.
We only see this in this TLS test and not in any other max ops tests.