Package Base Details: mutter-performance

Git Clone URL: https://aur.archlinux.org/mutter-performance.git (read-only, click to copy)
Submitter: Terence
Maintainer: Terence (Saren, saltyming)
Last Packager: saltyming
Votes: 76
Popularity: 1.43
First Submitted: 2019-07-09 09:35 (UTC)
Last Updated: 2024-05-05 05:39 (UTC)

Pinned Comments

saltyming commented on 2022-03-22 09:37 (UTC) (edited on 2023-09-02 03:43 (UTC) by saltyming)

Please note that a debug option is disabled in this package.

To disable building the docs package, set an env: _disable_docs=y

To enable the check() process, set an env: _enable_check=y


If the building process is getting failed on check() like

83/114 mutter:core+mutter/backends/native / native-unit TIMEOUT 180.01s killed by signal 15 SIGTERM

then you might want to do one of these:

0) Unset an env: _enable_check=y

1) Kill your pipewire session manager; killall $(pacman -Qq pipewire-session-manager).

2) Reboot the machine.

3) Pass a variable --nocheck to makepkg (which can be passed along with --mflags first if you are using paru) to temporarily disable a check() process.

4) Add a line options=(!check) to the package's PKGBUILD file to disable a check() process.

And try again.

Terence commented on 2020-08-31 16:26 (UTC) (edited on 2020-08-31 16:26 (UTC) by Terence)

@NettoHikari or anyone unable to compile with the following error:

lto1: internal compiler error: bytecode stream: expected tag identifier_node instead of LTO_UNKNOWN

You need to rebuild sysprof and then try again.

Reference: https://bugs.archlinux.org/task/67686.

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 .. 54 55 56 57 58 59

Saren commented on 2017-10-24 18:23 (UTC)

@jeckhack Prismatik (monitor backlight control program which captures screen constantly) still makes gnome-shell lag without reverting the mutter commit.

jeckhack commented on 2017-10-24 01:31 (UTC)

In fact, I had time to investigate my problem a bit further, and I think that problem isn't in opengl, but in Nvidia PowerMizer and mutter affecting programs' performance when nvidia card drops frequencies on idle. So, when you run benchmark, nvidia raises its frequencies to max and you don't notice any difference. But if you run some not-so-demanding game or app (i.e. terraria) You will notice that when nvidia drops frequencies, game starts to lag. The same happens with chromium. This behavior is fixed by reverting the commit from 781835 bugreport. You can minimize this behavio without reverting commit by enabling triplebuffer in nvidia. I created a bugreport on gnome: https://bugzilla.gnome.org/show_bug.cgi?id=789186

butler360 commented on 2017-10-22 17:25 (UTC)

In case anyone else runs into this bug, I had to add 'export PYTHONPATH="/usr/share/glib-2.0"' to the PKGBUILD to get this to build. https://bugs.archlinux.org/index.php?do=details&task_id=55915 That said, I did Unigine Valley benchmark before and after installing this and it make basically zero difference. I got a score of 1312 before and 1314 after. Is there a better way to benchmark this? I'm on a GTX 970.

jeckhack commented on 2017-10-16 12:26 (UTC) (edited on 2017-10-16 13:00 (UTC) by jeckhack)

Hi! Just take PKGBUILD from ABS, then add: git revert -n 383ba566bd7c2a76d0856015a66e47caedef06b6 to prepare() No need for a patch. P.S. This revert is a real lifesaver. Without it my OpenGL performance is plain awful on gtx960(!). Even Chromium scrolling at 30 fps.

Terence commented on 2017-10-16 00:40 (UTC) (edited on 2017-10-16 00:41 (UTC) by Terence)

@Saren I think it would be better to use https://gist.github.com/DeadMetaler/ec2afaed0e5e1a858e505af1cf5eca04 which respects the fact that it is not a fix but the revert of a previous commit.

Saren commented on 2017-10-13 18:14 (UTC)

Updated mutter to 3.26.1+7+g41f7a5fdf-1 to match upstream PKGBUILD. It is now much more stable with nvidia prop driver.

ciupenhauer commented on 2017-10-06 17:08 (UTC)

anyone got any ideas why the 3.26 update brought extra issues with dragging? it just hangs and frame drops when doing overview or dragging. This patch fixes the general slowness but now there's another issue I didnt have with 3.24

m110s commented on 2017-10-06 16:52 (UTC)

Thanks mate! No lag, but cpu spikes are still there when moving window. All in all much better experience with nvidia blob driver.

ciupenhauer commented on 2017-10-06 16:50 (UTC)

Thank you s.o. f.u.c.k.i.n. much! this is the second time new gnome version comes out and completely tanks my performance. this is just out of my brains how something like this is possible

Saren commented on 2017-10-06 15:21 (UTC)

This package applies the patch from https://gist.github.com/DeadMetaler/12622bf9415c1100f2d436ffbd6778c6 to workaround https://bugzilla.gnome.org/show_bug.cgi?id=781835 as to improve gnome-shell/mutter performance in some cases. (Prismatik + nvidia driver?)