Details
-
Bug
-
Resolution: Duplicate
-
Critical
-
4.5.0
-
Untriaged
-
Yes
Description
I noticed a regression in the following test:
Secondary index stale=false scan latency(ms), 1 bucket x 20M x 2KB, non-DGM, 14.4K Gops/sec, 3.6K mutations/sec, single index
It was 266.99 in build 1448 and jumped to 2693 in build 1613 and later.
If confirmed, please reassign.
Attachments
Issue Links
- relates to
-
MB-18744 2i stale=false scan latency fdb test - queryport i/o timeout
- Closed