I notice exactly the same thing.
Comparing to updating the autogroup priority, an alternative approach may be to use a different schedule policy, specifically SCHED_IDLE, so that it only uses idle resources after all other processes. I think this is probably the recommended approach in general.
Search found 1 match
- Sat Mar 14, 2020 1:22 pm
- Forum: V7.5.1 Public Release Windows/Linux/MacOS X [deprecated]
- Topic: Linux and Process Scheduler Autogroups
- Replies: 1
- Views: 1472