We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When people first turn on the reaper, it monopolizes their CPU.
Add some sort of limit to how fast the reaper runs so that it runs slower, but leaves cpu/ram available for other processes.
e.g. Throttle the reap at 2x what’s needed to keep up with new stuff. Might be tricky depending on how it batches.
It does a delete all. Maybe we could add a limit.
The text was updated successfully, but these errors were encountered:
paulbellamy
Successfully merging a pull request may close this issue.
What problem does your feature solve?
When people first turn on the reaper, it monopolizes their CPU.
What would you like to see?
Add some sort of limit to how fast the reaper runs so that it runs slower, but leaves cpu/ram available for other processes.
e.g. Throttle the reap at 2x what’s needed to keep up with new stuff. Might be tricky depending on how it batches.
It does a delete all. Maybe we could add a limit.
What alternatives are there?
The text was updated successfully, but these errors were encountered: