@jadahl some further questions if you don’t mind.
When using xrandr to achieve fractional scaling on xorg, some scaling factors are extremely demanding. For example, in order to achieve 1.5x in my external UHD monitor, 3840 * 2 / 1.5
= 5120 pixels width are required, and 2160 * 2 / 1.5 = 2880 height are required. It’s very noticeable, mainly as increased stuttering for the overview animation, when compared to 1.75x and, of course, 2x. I understand you need to produce more pixels if you want a smaller scale because more stuff will fit the screen.
Now, my questions: will this be the same under Wayland? If I set 1.5 scaling factor, will most of my apps (suppose they are maximized or full screen) be rendering about 5000x3000 pixels? Why would one expect this to be faster / less-demanding than my current xrandr workaround? I’m asking this because of a conversation I had in a PR, in which it was stated that all this won’t have the same penalty on Wayland that it has now using the RandR protocol, but I’m failing to grasp how can it be so. Maybe there are other optimizations in place, but my confusion is about the specific fact that you still have to produce more in order to sample.
Thanks again.