Search before asking
Fluss version
0.9.0 (latest release)
Please describe the bug 馃悶
remove_orphan_files assigns each scan subtask a minimum filesystem operation rate of 1/s. When the scan parallelism exceeds the configured total rate, this increases the aggregate rate above the requested limit.
For example, a total rate of 3 operations/s with parallelism 8 results in an aggregate target of 8 operations/s.
Solution
Allow fractional per-subtask rates by dividing the configured total rate by the scan parallelism, while retaining the existing best-effort rate-limiting semantics.
Are you willing to submit a PR?
Search before asking
Fluss version
0.9.0 (latest release)
Please describe the bug 馃悶
remove_orphan_files assigns each scan subtask a minimum filesystem operation rate of 1/s. When the scan parallelism exceeds the configured total rate, this increases the aggregate rate above the requested limit.
For example, a total rate of 3 operations/s with parallelism 8 results in an aggregate target of 8 operations/s.
Solution
Allow fractional per-subtask rates by dividing the configured total rate by the scan parallelism, while retaining the existing best-effort rate-limiting semantics.
Are you willing to submit a PR?