Originally posted by Britoid
View Post
Announcement
Collapse
No announcement yet.
New EEVDF Linux Scheduler Patches Make It Functionally "Complete"
Collapse
X
-
Originally posted by uid313 View PostGreat, but will my system still freeze under heavy load?
Under heavy load my system freezes to the point that I can't move my mouse cursor, I cannot switch to another virtual terminal, and I cannot kill the offending process. All I can do is wait or REISUB.
I had high hopes for some of the touted better scheduler / load responsiveness etc. stuff actually handling some of the typical desktop-user bad-cases but apparently not IME so far.
All it'd take is either ex-post-facto (or ab initio!) "de-nice-ing" (et. al.) memory / CPU hog processes to be more likely to swap or schedule at lower priority than interactive terminals, lightweight persistent desktop stuff you probably need / want to work as a priority, etc.
Maybe a bit of proactive monitoring as to the way your processes / programs are using resources and looking out for actual / impending bad cases and prompting the user for a preferable strategy (kill / restart / suspend job, deprioritize more, whatever) before / unless it gets so bad interactivity is just gone at which point it should at least maintain THAT.
It almost seems like wrt. things like errant browsers the best thing would be some kind of sandbox / container / configuration where they just HAVE to stay within a predefined RAM / CPU limit no matter what. If they have to swap (without affecting the rest of the system!) stuff to keep that, great, but in no way do I want a browser taking more than 50% of my CPU or 30% of my RAM e.g. Perhaps quotas / cgroups / something gives something closer to that choice without full virtualization (which itself wouldn't be bad other than the GPU / windowing fiascos).
- Likes 1
Comment
-
Originally posted by uid313 View PostGreat, but will my system still freeze under heavy load?
Under heavy load my system freezes to the point that I can't move my mouse cursor, I cannot switch to another virtual terminal, and I cannot kill the offending process. All I can do is wait or REISUB.
- Likes 6
Comment
-
Originally posted by timrichardson View PostThat sounds like out of ram rather than CPU. MGLRU should have made that much better for you. Look into your swap settings and make sure your kernel has activated MGLRU
Comment
-
Originally posted by Quackdoc View PostMassive +1, I've been using scx_lavd while gaming on my ryzen 2600, the performance difference when im running updates from the AUR is quite literally 30~fps to 55fps (for some reason it will never get to 60fps even when no load, but sits comfortably close to it) Rustland hasn't been super useful to me.
- Likes 3
Comment
-
Originally posted by arighi View Post
Can you provide more details about your specific workload / game? I'd be interested to reproduce it and see if we can improve rustland also for this particular case (maybe you could also open a new issue at https://github.com/sched-ext/scx/issues if you can). Thanks!
- Likes 2
Comment
-
Originally posted by npwx View PostHe seems to be rather angry. Whether you like systemd or not, it seems to have no relevance at all regarding the stability of his patches. The other wording like "puking all over the place" reinforces that impression.
I'd much rather learn what "Without something like this EEVDF will simply not work right" means specifically, given that it has been merged without it.
Comment
-
Originally posted by pong View Post
Yeah, same here. Notably also OOM / low memory cases as well. (…)
You can increase RAM usage efficiency with UKSM patch in conjunction with uksmd.
Originally posted by juxuanu View PostI still miss MuQSS.
I don't, its frametimes sucked.
- Likes 2
Comment
-
Originally posted by timrichardson View Post
That sounds like out of ram rather than CPU. MGLRU should have made that much better for you. Look into your swap settings and make sure your kernel has activated MGLRU.
I use the Ubuntu kernel so I don't know whether it has MGLRU activated or not. I do not have a swap. Running swapon --show outputs nothing.
Comment
Comment