Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-41020

Tweak or fuzz storage engine tunable parameters in testing

    • Fully Compatible
    • Execution Team 2020-09-21, Execution Team 2020-10-05, Execution Team 2020-10-19, Execution Team 2020-11-02, Execution Team 2020-11-16

      This ticket tracks a list of tunable parameters in both MongoDB and WiredTiger that can be changed or fuzzed during testing to increase coverage.

      Here's a start:

      • setParameter wiredTigerCursorCacheSize. We should run tests when this is set to 0 to disable cursor caching.
      • setParameter wiredTigerSessionCloseIdleTimeSecs. This is already set to 5 sec in debug builds.
      • setParameter wiredTigerConcurrentWrite/ReadTransactions. We already lower this to 64 in certain test suites.
      • WiredTiger file_manager parameters to wiredtiger_open (i.e. close_handle_minimum, close_idle_time, and close_scan_interval). This would introduce more aggressive file handle sweeps.
      • WiredTiger cache eviction parameters: eviction_target, eviction_trigger, eviction_dirty_target, eviction_dirty_trigger. These parameters are a function of the cache size which is already pretty low in most of our tests (1GB), so tweaking these may not be as effective as other options.

            brian.deleonardis@mongodb.com Brian DeLeonardis (Inactive)
            louis.williams@mongodb.com Louis Williams
            2 Vote for this issue
            10 Start watching this issue