-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
Affects Version/s: 3.4.9
-
Component/s: WiredTiger
-
ALL
-
-
(copied to CRM)
Periodic drops in throughput can be observed during checkpoints while running with an artificial workload and specific WiredTiger tuning parameters enabled.
I've attached diagnostic.tar.gz that shows this behavior. At around 2017-10-20T20:10:08.587Z the following command was executed:
db.adminCommand({setParameter: 1, wiredTigerEngineRuntimeConfig:"file_manager=(close_handle_minimum=100,close_idle_time=300,close_scan_interval=30)"});
After reaching steady state, we see the following:
Additionally, from perf, we can see that after making this parameter change, a single cpu core (12.5% of the total) is consistently fully utilized running eviction:
start_thread+0xffff017a586c80c5 __wt_thread_run+0xffff5458d1e2e016 __wt_evict_thread_run+0xffff5458d1e2e951
- is duplicated by
-
WT-5479 Checkpoint schema lock can cause long stalls in command execution on systems with many active data handles
- Closed
- is related to
-
SERVER-40773 Slow queries every 80s under moderate load
- Closed
- related to
-
SERVER-32890 Background index creation sometimes block whole server for dozen of seconds (even with empty collections)
- Closed
-
WT-6421 Avoid parsing metadata checkpoint for clean files
- Closed