Package Details: mutter-performance-devkit 49.0-1

Git Clone URL: https://aur.archlinux.org/mutter-performance.git (read-only, click to copy)
Package Base: mutter-performance
Description: GNOME Mutter Development Kit
Upstream URL: https://gitlab.gnome.org/GNOME/mutter
Licenses: GPL-2.0-or-later
Submitter: Terence
Maintainer: glorious-yellow
Last Packager: glorious-yellow
Votes: 74
Popularity: 0.000005
First Submitted: 2019-07-09 09:35 (UTC)
Last Updated: 2025-09-26 01:43 (UTC)

Pinned Comments

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 .. 65 Next › Last »

deezid commented on 2019-01-31 09:46 (UTC)

@DeadMetaler, haha, just had the same idea!

deezid commented on 2019-01-31 09:45 (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

DeadMetaler commented on 2019-01-31 09:42 (UTC)

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

Terence commented on 2019-01-31 08:32 (UTC)

@deezid how does this new version compare to the previous ones?

Terence commented on 2019-01-31 07:59 (UTC)

I disabled 168 again because even with the patch supposed to fix it, moving windows around with 500Hz/1000hz mouse is horrible.

Terence commented on 2019-01-31 07:40 (UTC)

@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?

deezid commented on 2019-01-30 20:47 (UTC)

@Terence with enabled revert patch and enabled 168 (commit cd280c30) it runs fantastic here.

Terence commented on 2019-01-30 15:03 (UTC)

@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...

glorious-yellow commented on 2019-01-30 14:58 (UTC) (edited on 2019-01-30 14:58 (UTC) by glorious-yellow)

I believe we can conditionally apply revert.patch based on the graphics card.

pacman -Q nvidia && patch -Np1 -i ../revert.patch || true may work.

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