The execution layer opens WiredTiger with an eviction thread max and min of 4. Which was decided ~6.5 years ago in SERVER-16602. Given that a lot has changed in the code base since then we should review the default settings for the connection open to WiredTiger, and potentially review the collection create settings.

Additionally from a technological standpoint machines are generally faster and have more resources available. I am specifically interested in the eviction threads min / max configuration. Stressful workloads on large machines could utilize more than that, which would avoid pulling application threads into eviction as frequently.

Other values of interest are:

• Eviction targets, dirty target, clean target.
• Leaf page max
• Memory page max
• Prefix_compression
• Split_pct

I think since SERVER-16602 a lot of these configurations are now exposed to users and can be configured manually as such they aren't as interesting for review.

As for the work here, I think we'd need to tune the values, run perf tests, collate the data and then make a decision for which value is best. This is potentially a lot of work and could be split into tickets for each configuration.