You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 23, 2023. It is now read-only.
I use ananicy to renice user bash shells to a lower priority, but keep ssh at a high priority. This becomes a problem when some shell script has a lot of loops, or repeated shell calls. Each new spawn of bash uses CPU cycles, and ananicy is trying to renice every one, and ananicy then starts eating up my CPU as well. Ananicy ends up consuming as much, if not more CPU than the actual processes being run.
This type of event could happen with any other program being programmatically looped on the system, not just bash. Renicing every process immediately as it is spawned may not always be necessary nor desirable. It would be valuable to have an option to tell ananicy, "only renice processes every X number of seconds"
Interval Wait X Seconds To Renice Processes Again
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I use ananicy to renice user bash shells to a lower priority, but keep ssh at a high priority. This becomes a problem when some shell script has a lot of loops, or repeated shell calls. Each new spawn of bash uses CPU cycles, and ananicy is trying to renice every one, and ananicy then starts eating up my CPU as well. Ananicy ends up consuming as much, if not more CPU than the actual processes being run.
This type of event could happen with any other program being programmatically looped on the system, not just bash. Renicing every process immediately as it is spawned may not always be necessary nor desirable. It would be valuable to have an option to tell ananicy, "only renice processes every X number of seconds"
Interval Wait X Seconds To Renice Processes Again
The text was updated successfully, but these errors were encountered: