mirror of
https://github.com/trapexit/mergerfs.git
synced 2026-11-19 22:46:34 -05:00
The hill-climb monitor samples throughput, perturbs thread count by +/-1, and checks whether throughput improved. But between samples, other mechanisms (fast-path pressure grow, idle self-exit) can also change the thread count. The monitor had no way to distinguish its own perturbation's effect from these external changes, which could cause it to reinforce or reverse direction based on unrelated scaling. Track the expected thread count after each perturbation. At the next sample, compare the actual count to the expected one. If they differ, external scaling occurred — skip the throughput attribution, reset the decline streak, and re-baseline from the current count. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| acutest | ||
| boost | ||
| CLI11 | ||
| fmt | ||
| khash | ||
| libfuse | ||
| nonstd | ||
| rapidhash | ||
| scope_guard | ||
| subprocess | ||