(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?