• Oran Agra's avatar
    Adjustments for active defrag defaults and tuning · 0bc3dab0
    Oran Agra authored
    Reduce default minimum effort, so that when fragmentation is just detected,
    the impact on the latency will be minor.
    
    Reduce the default maximum effort, mainly to prevent a case were a sudden
    massive deletions, won't trigger an aggressive defrag that will cause latency.
    
    When activedefrag is disabled mid-run, reset the 'running' info field, and
    clear the scan cursor, so that when it'll be re-enabled, a new fresh scan will
    start.
    
    Clearing the 'running' variable is important since lowering the defragger
    tunables mid-scan won't help, the defragger only considers new threshold when
    a new scan starts, and during a scan it can only become more aggressive,
    (when more severe fragmentation is detected), it'll never go less aggressive.
    So by temporarily disabling activedefrag, one can lower th the tunables.
    
    Removing the experimantal warning.
    0bc3dab0
server.h 110 KB