After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 785486 - Gnome animations choppy with low frame rate
Gnome animations choppy with low frame rate
Status: RESOLVED OBSOLETE
Product: gnome-shell
Classification: Core
Component: overview
3.24.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2017-07-27 10:06 UTC by harish.hyma
Modified: 2021-07-05 14:36 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description harish.hyma 2017-07-27 10:06:06 UTC
Running Gnome with wayland here on Arch Linux and the animations seem very choppy to begin with. I've scoured over every forum to in search for a solution. It becomes unbearable after running the computer for a few hours. The computer uses intel HD 5500 integrated graphics. I'm sure the computational resources required for the overview animation and the show applications animation can be taken care of by all latest intel processors. 

I find it ridiculous how this issue hasn't been solved it. However I do understand that there are more pressing problems with gnome. That being said, I believe that user experience should also be given importance. It became clear to me that the gnome team does not have enough people working on ensuring smooth performance. 

please don't misunderstand me. The people behind gnome have done an amazing job to build gnome to what it is now. I applaud them for their service and contribution. However, it won't hurt to have someone dedicated to fixing animation issues. If it can't be fixed it should be removed completely.
Comment 1 Alexander Mikhaylenko 2017-08-20 19:59:34 UTC
Duplicate of bug 725548 ?
Comment 2 Ray Strode [halfline] 2017-08-21 13:57:30 UTC
does 

$ cat /sys/class/drm/card0/gt_max_freq_mhz | sudo tee /sys/class/drm/card0/gt_min_freq_mhz 

resolve the problem ? If so, might be https://bugs.freedesktop.org/show_bug.cgi?id=102199
Comment 3 harish.hyma 2017-08-21 14:20:54 UTC
I'm sorry guys, I forgot to give details of my cpu.

Its Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz which can turboboost to 2.7GHz.

I've manually edited /sys/class/drm/card0/gt_min_freq_mhz to increase min frequency from 450 to 800. The max frequency is apparantly 900MHz. 

What does this following command do exactly? does it just make min frequency the same as max frequency?: 
cat /sys/class/drm/card0/gt_max_freq_mhz | sudo tee /sys/class/drm/card0/gt_min_freq_mhz 

How would this affect energy useage? Thanks for giving this bug some importance. I appreciate the effort of all the developers involved in this!
Comment 4 harish.hyma 2017-08-21 14:31:37 UTC
Please not that after changing to frequency and restarting, the minimum frequency returns to a default of 450MHz. Anyways to make this permanent?
Comment 5 Daniel van Vugt 2018-03-30 07:07:33 UTC
Your system might be CPU-bound or GPU-bound. I know gnome-shell is fairly CPU hungry during animations and in St rendering. However if your screen resolution isn't too high that shouldn't be the main issue...

A third issue is that mutter is algorithmically bound to schedule animations in a choppy way. A fix for that is here:

https://gitlab.gnome.org/GNOME/mutter/merge_requests/26
Comment 6 Daniel van Vugt 2018-03-30 07:09:52 UTC
Oh and if you're using Wayland then the Wayland backend has a list of performance problems which I'm tracking here:

https://trello.com/c/Q6JYXPPs

So I'd personally recommend using Xorg logins for now.
Comment 7 GNOME Infrastructure Team 2021-07-05 14:36:24 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of  gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/

Thank you for your understanding and your help.