| Git Clone URL: | https://aur.archlinux.org/mutter-performance.git (read-only, click to copy) |
|---|---|
| Package Base: | mutter-performance |
| Description: | A window manager for GNOME | Attempts to improve performances with non-upstreamed merge-requests and frequent stable branch resync |
| Upstream URL: | https://gitlab.gnome.org/GNOME/mutter |
| Licenses: | GPL-2.0-or-later |
| Groups: | gnome |
| Conflicts: | mutter |
| Provides: | libmutter-15.so, mutter |
| Submitter: | Terence |
| Maintainer: | Terence (Saren, saltyming) |
| Last Packager: | saltyming |
| Votes: | 78 |
| Popularity: | 0.172346 |
| First Submitted: | 2019-07-09 09:35 (UTC) |
| Last Updated: | 2024-12-23 10:16 (UTC) |
Seems like with 168 applied in my "smoothness test" (playing YouTube in 4K in one windows, scrolling in another), everything stays smoother. Without 168 it becomes quite messy after a few seconds.
Another question, wondering if 117 applies at all? There are lots of messages before compiling about not being able to apply it? Why not use the 3.30 branch version of the patch instead? 9a466f28
error: could not apply 8655bc5d8... clutter: Fix offscreen-effect painting of clones
Use this 3.30 based branch https://gitlab.gnome.org/vanvugt/mutter/commits/fix-offscreen-clones-3.30
@deezid how does this new version compare to the previous ones?
I disabled 168 again because even with the patch supposed to fix it, moving windows around with 500Hz/1000hz mouse is horrible.
@deezid thanks for your feedback. I updated it again with some new performance patches as well as 168 enabled by default as 365 should fix the problem it accentuated. Would you mind giving your feedback about the need to revert the commit to vanvugt?
@Terence with enabled revert patch and enabled 168 (commit cd280c30) it runs fantastic here.
@glorious-yellow Thanks for the report, it's updated. I guess we could do that but I wanted to let people try how it felt without the revert as ultimately all those performance patches are trying to fix what this commit made worse...
I believe we can conditionally apply revert.patch based on the graphics card.
pacman -Q nvidia && patch -Np1 -i ../revert.patch || true may work.
Commit hash for https://gitlab.gnome.org/GNOME/mutter/merge_requests/399/commits changed again
Pinned Comments
saltyming commented on 2022-03-22 09:37 (UTC) (edited on 2024-10-22 08:27 (UTC) by saltyming)
If you have a problem during any system update with
mutter-performance&gnome-shell-performance, please installmutter&gnome-shellpackages from the main repository and do full upgrade first, then build the performance packages later.If you are using [gnome-unstable] and [extra-testing] repositories, use mutter-performance-unstable
The default patch list includes "Dynamic triple buffering(!1441)", "text-input-v1(!3751)".
Latest Dynamic triple buffering patch has several included MRs from the main development branch to achieve maximum performance.
To enable a specific MR in the Merge Requests List, add an line "_merge_requests_to_use+=('<MR number>')" at the end of PKGBUILD. (Because if you edit the line directly you can be able to end up with merge conflict upon updates.)
You can see some patches' git history here: https://git.saltyming.net/sungmg/mutter-performance-source/
Saren commented on 2018-08-30 14:52 (UTC) (edited on 2020-10-06 05:50 (UTC) by Saren)
If you are getting errors like
fatal: bad revision '73e8cf32'while building this package, refer to PKGBUILD and see which patches caused this. Then, go to the related URLs, replace the commit hashes. If there are conflicts, comment out the patches.Please notify me in comment section if this happens.
The optional performance patches are by default enabled.
A package for gnome-shell performance patches: https://aur.archlinux.org/packages/gnome-shell-performance/