Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add benchmark to README.md file #81

Open
qarmin opened this issue Apr 15, 2023 · 1 comment
Open

Add benchmark to README.md file #81

qarmin opened this issue Apr 15, 2023 · 1 comment

Comments

@qarmin
Copy link

qarmin commented Apr 15, 2023

In readme file I see

These changes result in a noticeable improvement in the experienced smoothness
and performance of applications and games.

but how big is improvement on older/newer machines? 0.05, 0.5, 5 or 50%

Adding benchmark like https://flightlessmango.com/benchmarks/rM7Rfu4swVQ would let users know what kind of increase (or decrease) in performance they can expect

@mmstick
Copy link
Member

mmstick commented Apr 15, 2023

There's a lot of variables that affect the outcome, so it can't be described in a single statistic. It will vary based on the configuration you use, the hardware you have, and the kind of workload you're doing with it.

The service is changing priorities of processes automatically, so you will see some improvement in response times and throughout for the prioritized processes, and reduced performance from background processes. How much of an improvement will depend on how much resources were being absorbed by the background processes that could have been given to the foreground processes.

The main goal is to eliminate possible causes of microstutters that can happen if a background service or task suddenly starves the system of resources. And the next update to be merged will extend the prioritization to pipewire-connected processes to ensure they're able to play audio without stutters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants