mirror of
https://github.com/trapexit/mergerfs.git
synced 2026-10-26 19:01:56 -04:00
The previous ordering (enqueued first, then completed) meant a task completing between the two loads would inflate the pending count. For scaling heuristics, over-reporting pressure is worse than under-reporting: it can trigger unnecessary thread creation. Swap the load order so completed is read first. A completion between the two loads now reduces the delta toward zero, which is the safer direction for autoscale decisions. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| acutest | ||
| boost | ||
| CLI11 | ||
| fmt | ||
| khash | ||
| libfuse | ||
| nonstd | ||
| rapidhash | ||
| scope_guard | ||
| subprocess | ||