Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: User Error
-
7.1.0
-
Untriaged
-
-
1
-
Unknown
Description
Build: 7.1.0-1745
Test:
1 bucket x 50M x 1KB, 10K KV ops/sec, 1000 indexes, Plasma, s=1 c=100, 128 Concurrency, N2N=all
TLS | Non-TLS | |
---|---|---|
Scan throughput | 433518.6 | 176816.6 |
90th Latency | 0.79 | 1.18 |
95th Latency | 1.15 | 1.66 |
Test jobs | http://perf.jenkins.couchbase.com/job/hemera/3241/console | http://perf.jenkins.couchbase.com/job/hemera/3254/console |
Cbmonitor comparison: http://cbmonitor.sc.couchbase.com/reports/html/?snapshot=hemera_710-1745_apply_scanworkload_cdb8&snapshot=hemera_710-1745_apply_scanworkload_f36d
seeing bucket CPU is down from 60% to 20% for TLS
Vikas Chaudhary , Good that you raised this bug. From the test logs, the rows throughput is "0" for the test with TLS=all enabled. This means that none of the indexes are getting scanned.
From http://perf.jenkins.couchbase.com/job/hemera/3241/consoleFull
23:06:27 2021-11-26T09:36:27 [INFO] Scan throughput: 433518.60375465493
23:06:27 2021-11-26T09:36:27 [INFO] Rows throughput: 0.0
23:06:27 2021-11-26T09:36:27 [INFO] Total Recs in Mem 761154836
From http://perf.jenkins.couchbase.com/job/hemera/3254/console
**
21:21:31 2021-11-27T07:51:58 [INFO] Scan throughput: 176816.64002626156
21:21:58 2021-11-27T07:51:58 [INFO] Rows throughput: 176822.5341107319
21:21:58 2021-11-27T07:51:58 [INFO] Total Recs in Mem 745375547