Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
7.1.0
-
Untriaged
-
1
-
Unknown
Description
PlasmaDGM tests are regressed since 7.1.0-1887
Test:
Secondary Scan Throughput (scanps) 1 bucket x 100M x 1KB, 2K KV ops/sec, 1000 indexes, 20% RR, Plasma, s=1 c=100
7.1.0-1885 | 7.1.0-1887 | 7.1.0-1941 |
---|---|---|
205742.9 | 129,249.5 | 139555 |
Latest run: http://perf.jenkins.couchbase.com/job/hemera/3536/console
Attachments
Issue Links
- relates to
-
MB-50771 Working set tracking for in-memory compression
-
- Open
-
For Gerrit Dashboard: MB-50250 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
168868,9 | MB-50250: Compress after swapin only if under memory pressure | unstable | plasma | Status: MERGED | +2 | +1 |
169807,4 | MB-50250: Add plasma CompressMemoryThreshold config | unstable | indexing | Status: MERGED | +2 | +1 |
Regression is due to decompression overhead. From build 7.1.0-1887 onwards, plasma will compress on swapin. If scans accesses only compressed pages, they will be slower due to decompression overhead. This can occur even when there is sufficient memory between usage and quota. To overcome this, compression on swapin can be performed only when there is memory pressure and with this patch, the performance for this test is back to normal. But, this can be bad for cases where the hot set does not change or gets swapped-out/swapped-in and the hot set does not fit in quota as in the case of the new compression tests. In these tests, regression is observed due to lower resident ratio from not compressing.