Package Details: mutter-performance 1:46.2+r17+gec5444f541-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
Groups: gnome
Conflicts: mutter
Provides: libmutter-14.so, mutter
Submitter: Terence
Maintainer: Terence (Saren, saltyming)
Last Packager: saltyming
Votes: 77
Popularity: 1.23
First Submitted: 2019-07-09 09:35 (UTC)
Last Updated: 2024-06-27 09:39 (UTC)

Dependencies (66)

Required by (13)

Sources (5)

Pinned Comments

saltyming commented on 2022-03-22 09:37 (UTC) (edited on 2024-05-26 07:35 (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. Note that it can be problematic in some versions/setups.

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 may 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 the check() process.

4) Add a line options=(!check) to the package's PKGBUILD file to disable the 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 .. 43 44 45 46 47 48 49 50 51 52 53 .. 60 Next › Last »

ciupenhauer commented on 2019-01-16 22:12 (UTC)

installed deezid's pkgbuild with mixed results: better scrolling inside browsers, smoother window drag, smoother open/close animations. Worse overview animations , still slow or slower overview with youtube video playing, worse overall feeling. So not quite there yet.

ciupenhauer commented on 2019-01-16 17:09 (UTC)

thanks @deezid trying your build now

deezid commented on 2019-01-16 16:41 (UTC) (edited on 2019-01-16 19:07 (UTC) by deezid)

Please take a look here https://forum.manjaro.org/t/how-to-gnome-mutter-performance-patches/71989

Altered to the PKGBUILD to make it work with latest patches inside the 3.30 branch. Also removed the "NVIDIA-fix" which just caused harm and replaced it by patch 281 by Daniel van Vugt.

V4 fixed the last remaining issues.

The difference honestly is quite insane, doesn't really feel like Gnome anymore - in a good way.

deezid commented on 2019-01-16 02:26 (UTC)

Final fix found, thanks to Daniel van Vugt (281.patch)

The revert.patch has to be deleted since it causes more harm than it actually helps.

The 281.patch by Daniel van Vugt fixed the last piece of lag entirely. https://gitlab.gnome.org/GNOME/mutter/merge_requests/281.patch

deezid commented on 2019-01-15 21:13 (UTC)

Just noticed that with the revert patch the performance maybe still way better than before thanks to the other patches but it's not quite the same inside programs.

With the revert patch applied performance inside programs is amazing but dragging windows stutters at 30fps unless a video or animation is running at 60fps.

I wonder what exactly causes this behavior https://aur.archlinux.org/cgit/aur.git/tree/revert.patch?h=mutter-781835-workaround

deezid commented on 2019-01-15 13:57 (UTC) (edited on 2019-01-15 18:37 (UTC) by deezid)

Was able to install this patched version after updating the commit numbers in the pkgfile.

What I noticed is that apps like Chrome or Davinci Resolve are now insanely smooth but mutter or at least dragging windows itself is now terribly slow. I think it is locked to 30fps. The cursor itself is running at 60fps all the time. Animations aren't affected either - in fact they are smoother than ever, just dragging windows around while no 60p video or animation is running.

Interestingly enough if there's a video with 60fps playing behind and the foreground window is being dragged around, everything is smooth until I stop playback. If the video only has up to 30fps dragging windows is locked at 30fps again. Moving video players like MPC or VLC is also smooth while playing lower framerate video files.

Will take a look at the individual applied patches and hopefully figure out which one is causing it.

EDIT: The 60p video can even be running on another activity. Will maybe use this as a workaround lol - just kidding. Also noticed that even 8K60p runs perfectly smooth inside Chrome now while before even 4K60p wasn't possible - amazing!

Fixed it by uncommenting the actual NVIDIA fix. Am using the official 415.25 driver here using a 1080TI

beano commented on 2019-01-09 11:40 (UTC) (edited on 2019-01-09 11:41 (UTC) by beano)

build fails with fatal: bad revision for commits 8234efc0 and d2fbb9ff. commenting them out as stated by Saren enables you to build the package.

m110s commented on 2018-12-24 17:51 (UTC)

@Terence Works now without reverting merge.tool. Thanks a lot mate!

Terence commented on 2018-12-24 15:58 (UTC) (edited on 2018-12-24 15:59 (UTC) by Terence)

@m110s updated once more, please report if it works. My instruction with mergetool was a mistake because not everyone has this merge tool... You can revert it with git config --global --unset merge.tool although it shoudn't have much of an impact at this point.

m110s commented on 2018-12-24 11:53 (UTC) (edited on 2018-12-24 11:55 (UTC) by m110s)

New error:

error: could not apply 81952da6f... clutter: Fix offscreen-effect painting of clones
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add <paths>' or 'git rm <paths>'
hint: and commit the result with 'git commit'
Merging:
clutter/clutter/clutter-paint-volume.c
clutter/tests/conform/meson.build

Normal merge conflict for 'clutter/clutter/clutter-paint-volume.c':
  {local}: modified file
  {remote}: modified file
The merge tool p4merge is not available as 'p4merge'

earlier I followed you instruction:

git config --global merge.tool p4merge

« First ‹ Previous 1 .. 43 44 45 46 47 48 49 50 51 52 53 .. 60 Next › Last »