>uses Wayland for the first time and the RAM usage while actually doing work is almost halvedWhy does no one talk about this?
>>106444413Quads of TRUTH.>Why does no one talk about this?We do.
>>106444413is this while taking in account the wayland+compositor or just wayland?
>>106444435>Quads of TRUTHback to /pol/ newfag
>>106445808The joke was that those quads aren't "true" quads.
>>106445736Wayland using Sway which is a Compositor/WM compared to Qtile and i3 on X11 with a basic Picom. It seems that X11 keeps extra buffers and having the WM and Compositor separate adds more buffers.The only problem with Wayland is if you copy a large block of code from chromium it will crash, so you have to use wl-paste > file. Also screen sharing for electron apps requires a hacky third party fix via xwaylandvideobridge. However, those will likely be fixed in the near future.I also am impressed with Wayland smoothness. I've spent a lot of time tweaking Picom to get it looking smooth, but it's always missing that last few percent.
>>106445995>However, those will likely be fixed in the near futuretwo more years? XD
>>106445995sway is debian level stable at this point. bugs do get fixed but it can take a while. but its also a good thing if you dont want breaking changes or new bugs added to your wm. if you want a changes rolled out on a xfce timeline but for wayland, sway is the way to go.where as after updating hyprland today i needed to update an option in my config because its no longer valid.
>>106445886A bit too deep
>>106444413X11 is solved at this point and it's fucking trivial to spin up a window and do shit with it. I'm not learning a whole new api for 0 benefit and with a possible loss in portability in the process (last I checked certain things weren't even portable across Wayland implementations meaning I'll have to potentially remake shit for both kde and fucking gnome lol).
>>106446265> sway isMost of of us don’t even know or care what “sway” is. Never heard of it.You might was well just get together in a private discord server and cluck with each other like hens.Sorry, if “cluck” is some other wayland component, i didn’t mean to offend anyone to the point of self-flagellation or beyond.
>>106445995Picom itself uses more buffers for triple buffering. Gnome wayland does that as well. But anyways you can remove all of that extra memory usage by using picom in xrender mode instead of opengl in which case it will use less memory than sway. Thats true for applications on x11 in general. You can do all desktop applications rendering on the server to reduce memory usage. That's not possible on wayland.
>>106447535>>106444413Here is the memory usage of picom with xrender vs glx
>>106447535My understanding is that X-accelerated rendering is barely used at all, most modern applications just write to a frame buffer and tell X to show it on screen in a given position, which is why using X over SSH for complex applications sucks ass (it’s just sending a bunch of images, and the X wire protocol isn’t optimised for that).
>>106447561I’d be interested into whether the overall memory usage is the same though, it sounds like shifting to XRender would just move the buffers from picom to the X server, given that XRender is similar in nature to OpenGL
>>106447613The memory usage is reduced since it reduces the amount of buffers it uses but also because every application that uses opengl/vulkan has a large memory cost even without buffers. A graphics context uses a lot of memory. This is true on windows as well. When you use one process and share that it removes that overhead.>My understanding is that X-accelerated rendering is barely used at allIt's used by all gtk3 and qt applications.>most modern applications just write to a frame buffer and tell X to show it on screen in a given position, which is why using X over SSH for complex applications sucks assMost modern applications use opengl, but they can actually work well remote over ssh as well. It's just that most applications try to force direct rendering. There is an environment variable to overwrite that behavior in glx applications, to force indirect rendering. When the driver receives opengl operations from the client and indirect rendering is enabled it will redirect all opengl calls to the X server
>>106447675I forgot to quote >>106447593 for the quotes
>>106447561That is quite the difference. I'll have to try that out because I'm not trying to do anything fancy with Picom, just have basic compositing and not tap out my laptop's ram when I use it for work.
>>106446835Why would you be fucking gnome?
>>106447675I was (mistakenly) only referring to use of the X11 widgets being accelerated. I wasn’t aware that GLX could be coerce into rendering client side (X client/server terminology is annoying. Here I mean the remote user SSHing into another computer and running applications on it has GL rendering instructions sent to their machine)I also believe there’d definitely be an improvement, but that the difference from 66MB to <1MB is probably exaggerating the gain. I doubt the overhead of buffer management structures would be more than 20% of memory usage, the majority would just be holding frame buffer data, and that doesn’t change either way, only the record keeping would. I’d also be interested as to the downsides. I’m not familiar enough with X11 to know. My understanding of Wayland is that it essentially just acts as a system for applications to throw frame buffers around, and windowing and whatnot is built atop that (hence why it’s such a different beast from X11, and lacks a lot of the “batteries included” type stuff. At the end of the day it’s just an IPC spec)
>Quads of TRUTH.Fucking indians are browning the internet, mate, for fuck's sake
>>106448626I just checked memory usage of Xorg process now with picom xrender and it doesn't increase memory usage at all>>106447858If all you want is to fix tearing then you can enable the TearFree option in xorg settings instead. Unfortunately this hasn't been put in a release in the modesetting driver (despite being added 3 years ago and even enabled by default), but you can use the amd/intel x11 driver which has that option.
>>106445736Wtf are you talking about lmao
>>106451282>I just checked memory usage of Xorg process now with picom xrender and it doesn't increase memory usage at allTo be more specific, it doesn't increase ram usage but it does increase vram usage, but so does picom with glx. Picom with glx increases vram usage in xorg much more than xrender does and also uses vram in the picom process, so it ends up using 10 times more vram for glx than xrender.
