Details
-
Bug
-
Resolution: Won't Fix
-
Critical
-
None
-
4.5.0
-
Security Level: Public
-
Untriaged
-
Unknown
Description
For n1ql perf test (Q2, stale=false, build 858), we see fdb commit time ranges from 300ms to 10s. This seems to varies from run to run. For the same build, we have separate run that does not observe the long commit issue (but this run has the long pause issue).
Run 2221 (with long commit time issue)
http://perf.jenkins.couchbase.com/job/hades/2221/
Run 2166 (without long commit issue – but with long pause issue)
Attachments
Issue Links
- relates to
-
MB-17104 Q2 stale=false throughput performance test - OOM in thread start
- Closed
-
MB-18604 The indexer cannot be reached once the FDB indexes are built (initial build) for few minutes.
- Closed
-
MB-17105 Q2 stale=ok performance test - cgocall/compaction panic
- Closed
-
MB-19173 Initial and incremental build time regression for 5 indexes (fdb)
- Closed
-
MB-21542 Initial and incremental indexing in Watson is slower than in Sherlock (FDB)
- Closed
For Gerrit Dashboard: MB-17236 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
62676,3 | MB-17236 Enable the background flusher to reduce commit time | master | forestdb | Status: NEW | 0 | 0 |