[Bug 1226827] New: Switch to 1000Hz kernel timer frequency
https://bugzilla.suse.com/show_bug.cgi?id=1226827 Bug ID: 1226827 Summary: Switch to 1000Hz kernel timer frequency Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: rx2l5t+4zshakz4lenfc@sharklasers.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- This would be optimal for desktop usage, gaming, music production, and maybe some servers, potentially making these workloads more responsive, performant and power-efficient on Tumbleweed instead of the current default of 300Hz. Consider the rationale and additional kernel configuration posted here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051342 https://discourse.ubuntu.com/t/enable-low-latency-features-in-the-generic-ub... https://github.com/ValveSoftware/SteamOS/issues/1522 As far as I know, Android, ChromeOS, and Ubuntu have done this change -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1226827 https://bugzilla.suse.com/show_bug.cgi?id=1226827#c4 --- Comment #4 from nuts <rx2l5t+4zshakz4lenfc@sharklasers.com> --- (In reply to Jiri Wiesner from comment #3)
It there a specific use case (or a benchmark) that you are aware of, perhaps your own? We could work on addressing this use case before we start taking steps that change an option that potentially decreases throughput? On the other hand, Tumbleweed is not deployed on production servers of SUSE's customers so I think there is more leeway in terms of performance regressions.
I'm thinking of general desktop usage, gaming, and power efficiency, mostly. There should be improved response times in those cases and they *should* be more power efficient because the CPU enters an idle state faster, and there's a large gaming audience on Tumbleweed so far. According to the Ubuntu benchmarks I sent before, the nohz_full boot option could mitigate worse throughput, right? -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com