4 ms·
I wonder, does Wayland requires to allocate gigantic buffers for every window or it is possible to make a Wayland implementation that doesn't require tens of me
by codedokode 3y ago
I wonder, does Wayland requires to allocate gigantic buffers for every window or it is possible to make a Wayland implementation that doesn't require tens of megabytes of RAM? For example, is it possible to render window by tiles (of course only changed tiles) using a small 200×200 buffer? Is it possible to use a single buffer for all applications (which they use in turn)?
- phkahler 3y agoAll modern composited desktops have buffers per app, even on X11.
- codedokode 3y agoBut isn't this super expensive, especially when there are many windows and 4K resolution displays? I don't like that you need 10 buffers for 10 full-screen windows when you see only the topmost one.
- acdha 3y agoSay you have a dozen of full screen windows. That’s 3840 × 2160 × 3 bytes per window or 24MB, so our dozen windows take just shy of 300MB uncompressed. That’s not nothing, but it’s also a small fraction of the RAM on even a phone for one of the primary functions of the device, and the upside is that you avoid all kinds of nasty challenges coordinating updates and access between applications and the window server because there’s no shared state between applications and the window manager can do things like transparency, scaling, or all-windows switching views without any app involvement. Another way of looking at this, Apple did the same move over a decade ago with far more limited hardware and pretty much everyone loved it because the speed and stability boost was quite noticeable.
- deleted 3y ago[deleted]