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 .. 35 36 37 38 39 40 41 42 43 44 45 .. 64 Next › Last »

kode54 commented on 2019-04-11 06:42 (UTC)

Replace revision f5a1ec1c with 34fae0f5. This is only going to keep hurting more and more, as all of @vanvugt's PRs keep getting rebased constantly instead of getting accepted.

kerframil commented on 2019-04-05 12:01 (UTC)

Currently, f5a1ec1c is reported as a bad revision. Also, the rt-scheduler option doesn't appear to have any effect. As shown below, neither the main process nor any of its threads are using the RR scheduling class.

$ ps -C gnome-shell -Lo pid,cls,comm,command
  PID CLS COMMAND         COMMAND
  816  TS gnome-shell     /usr/bin/gnome-shell
  816  TS gmain           /usr/bin/gnome-shell
  816  TS gdbus           /usr/bin/gnome-shell
  816  TS dconf worker    /usr/bin/gnome-shell
  816 IDL gnome-s:disk$0  /usr/bin/gnome-shell
  816  TS JS Helper       /usr/bin/gnome-shell
  816  TS JS Helper       /usr/bin/gnome-shell
  816  TS JS Helper       /usr/bin/gnome-shell
  816  TS JS Helper       /usr/bin/gnome-shell
 7364  TS gnome-shell     /usr/bin/gnome-shell
 7364  TS gmain           /usr/bin/gnome-shell
 7364  TS gdbus           /usr/bin/gnome-shell
 7364  TS dconf worker    /usr/bin/gnome-shell
 7364 IDL gnome-s:disk$0  /usr/bin/gnome-shell
 7364  TS JS Helper       /usr/bin/gnome-shell
 7364  TS JS Helper       /usr/bin/gnome-shell
 7364  TS JS Helper       /usr/bin/gnome-shell
 7364  TS JS Helper       /usr/bin/gnome-shell

flomax commented on 2019-04-04 03:29 (UTC)

@Terence Cheers, and I now see where I went wrong too.

Terence commented on 2019-04-04 02:38 (UTC)

@flomax Thanks for reporting, it should be fixed.

flomax commented on 2019-04-03 23:07 (UTC) (edited on 2019-04-03 23:08 (UTC) by flomax)

Getting fatal: bad revision '14a27e87^..a40d7927'

Replacing a40d7927 with 6474593e or 966e062d did not fix, but build completes once whole line is commented out.

Terence commented on 2019-03-31 01:19 (UTC)

@Saren oups my bad! Updated so it doesn't apply by default.

Saren commented on 2019-03-30 14:09 (UTC)

@Terence Did you mean without _revert=0? _revert=0 still applies the patch I guess.

Terence commented on 2019-03-30 11:03 (UTC)

Thanks @ciupenhauer and @deezid for the heads-up, updated. @Saren this should render the commit revert useless. Can you try again with _revert=0 and report back?

deezid commented on 2019-03-28 20:08 (UTC)

@clupenhauer. That's what I thought. Skip the first !281 commit. https://bugzilla.gnome.org/show_bug.cgi?id=789186#c18

  # clutter-stage-cogl: Reduce output latency and reduce missed frames too [performance]
  # first commit replaced by !363
  # https://gitlab.gnome.org/GNOME/mutter/merge_requests/281
  git cherry-pick -n 186f16f8

  # Consolidate all frame throttling into clutter-stage-cogl [performance]
  # https://gitlab.gnome.org/GNOME/mutter/merge_requests/363
  git cherry-pick -n 577084a4^..c71e6523

ciupenhauer commented on 2019-03-28 20:05 (UTC)

According to Daniel van Vugt: "Also note the second commit of https://gitlab.gnome.org/GNOME/mutter/merge_requests/363 provides a fix for this bug too. It replaces the first commit of https://gitlab.gnome.org/GNOME/mutter/merge_requests/281"

Does that mean we can safely switch off patch 281 and use only 363?

« First ‹ Previous 1 .. 35 36 37 38 39 40 41 42 43 44 45 .. 64 Next › Last »