Ok, I found it. Tested with and without 383ba566 commit:
With this commit - nvidia drops frequencies and Chromium drops fps to 30, shell starts to lag. When nvidia raises frequencies on load, it's again 60fps. You can trigger load by switching\opening new windows. You can monitor nvidia frequency in parallel.
Without commit - nvidia drops frequencies, but Chromium is still smooth. gnome-shell fps drops to 30, you can clearly see it when moving Chromium window around the screen.
This is tested with and without HW acceleration in chromium.
So, you are right.
>> However, we are now off-topic. This bug is about CPU usage being too high.
Ok, I found it. Tested with and without 383ba566 commit:
With this commit - nvidia drops frequencies and Chromium drops fps to 30, shell starts to lag. When nvidia raises frequencies on load, it's again 60fps. You can trigger load by switching\opening new windows. You can monitor nvidia frequency in parallel.
Without commit - nvidia drops frequencies, but Chromium is still smooth. gnome-shell fps drops to 30, you can clearly see it when moving Chromium window around the screen.
This is tested with and without HW acceleration in chromium.
So, you are right.
>> However, we are now off-topic. This bug is about CPU usage being too high.
I see it now, thanks.