WT-2764 Replace write leaves phase of checkpoints. (#2876)

Instead, get multi-threaded writes by dialling down the eviction dirty trigger.

Change eviction_dirty_* defaults (to 20/5).

Make sure all files are available for eviction before starting fsync.

Take more care excluding clean files from checkpoints.

Only use scrubbing mode when there is minimal cache pressure.

Avoid penalizing read-only operations with dirty eviction targets.

Enable scrubbing when eviction is keeping space available in cache.

Add stats for checkpoint scrubbing phase.

Improve cache scrubbing with big caches and slow I/O.

Use the rate of bytes written from cache to decide how long to wait for
the dirty bytes to come down.

1 files changed, 4 insertions, 4 deletions

diff --git a/dist/api_data.py b/dist/api_data.py
index e1b877a1a35..1302247e88e 100644
--- a/dist/api_data.py
+++ b/dist/api_data.py
@@ -401,16 +401,16 @@ connection_runtime_config = [
                 vary depending on the current eviction load''',
                 min=1, max=20),
             ]),
-    Config('eviction_dirty_target', '80', r'''
+    Config('eviction_dirty_target', '5', r'''
         continue evicting until the cache has less dirty memory than the
         value, as a percentage of the total cache size. Dirty pages will
         only be evicted if the cache is full enough to trigger eviction''',
-        min=5, max=99),
-    Config('eviction_dirty_trigger', '95', r'''
+        min=1, max=99),
+    Config('eviction_dirty_trigger', '20', r'''
         trigger eviction when the cache is using this much memory for dirty
         content, as a percentage of the total cache size. This setting only
         alters behavior if it is lower than eviction_trigger''',
-        min=5, max=99),
+        min=1, max=99),
     Config('eviction_target', '80', r'''
         continue evicting until the cache has less total memory than the
         value, as a percentage of the total cache size. Must be less than