Package Details: mutter-performance 1:47.4-1

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.077814
First Submitted: 2019-07-09 09:35 (UTC)
Last Updated: 2025-01-15 11:01 (UTC)

Dependencies (66)

Required by (16)

Sources (4)

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 install mutter & gnome-shell packages 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/

Latest Comments

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 64 Next › Last »

Terence commented on 2019-10-28 16:28 (UTC)

@TheAifam5 @gedgon @ciupenhaue I added!719 and !762 which fixes one issue of !719. You need to add them to the _merge_requests_to_use array.

Terence commented on 2019-10-27 23:13 (UTC)

Alright tomorrow I'll add !719 as an optional MR.

theaifam5 commented on 2019-10-27 21:48 (UTC)

!719 is missing in PKGBUILD.

Terence commented on 2019-10-27 16:23 (UTC)

@Saren I introduced a new way of choosing what MR you want to use: Just add the proposed ones you want into the _merge_requests_to_use array.

gedgon commented on 2019-10-26 16:54 (UTC)

@ciupenhauer, Dan van Vugt mentioned here 1, that !719 revisit or rewrite is one of the goals for the 3.36. Till then, just try !719 as it is, and check if you are affected by the regressions that it triggers or causes.

ciupenhauer commented on 2019-10-25 14:52 (UTC)

any more news in !719?

gedgon commented on 2019-10-22 14:33 (UTC) (edited on 2019-10-22 14:34 (UTC) by gedgon)

@Terence Personalty, I haven't encountered any crashes caused by !719, these are probably limited to rare certain scenarios, and the performance difference is huge, so it's probably worth adding it on condition, just like !493. Some numbers on polaris @4k w/ GPU clock limited to 300/214/387/625MHz. FPS for an overview animation w/ 5 windows

mutter-3.34.1+27+g85f5db7e7 w/o !719 

*** FPS for MetaStage: 31 ***
*** FPS for MetaStage: 36 ***
*** FPS for MetaStage: 31 ***
*** FPS for MetaStage: 31 ***
*** FPS for MetaStage: 35 ***
*** FPS for MetaStage: 31 ***
*** FPS for MetaStage: 31 ***
*** FPS for MetaStage: 34 ***

mutter-3.34.1+27+g85f5db7e7 w/ !719 

*** FPS for MetaStage: 60 ***
*** FPS for MetaStage: 60 ***
*** FPS for MetaStage: 61 ***
*** FPS for MetaStage: 60 ***
*** FPS for MetaStage: 61 ***
*** FPS for MetaStage: 60 ***
*** FPS for MetaStage: 61 ***
*** FPS for MetaStage: 61 ***

Terence commented on 2019-10-20 23:06 (UTC)

@glitsj16 the updated version should contain the fix.

@gedgon Thanks, it seems like it was causing different problems that aren't all addressed at the time so I'm not applying it.

glitsj16 commented on 2019-10-09 03:00 (UTC) (edited on 2019-10-09 03:03 (UTC) by glitsj16)

[FYI] Latest version broke GNOME's Night Light functionality. On a daily/nightly basis I actually use https://aur.archlinux.org/packages/redshift-gnomerr-git, but when that broke, I tried the native Night Light, which was broken too. See https://gitlab.gnome.org/GNOME/mutter/issues/851 for my bug report. When I build mutter-performance from latest git master and revert the relevant MR, both work again.

gedgon commented on 2019-10-06 07:06 (UTC)

JFYI, !719 was reverted from master https://gitlab.gnome.org/GNOME/mutter/commit/97140ab6346bd29208e99c9c9aab892c2eec0e52

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 64 Next › Last »