A fast alternative to the picom X11 compositor - fastcompmgr #6039
Replies: 4 comments 1 reply
-
This looks interesting but how does one get rid of the screen tearing when using this compositor? |
Beta Was this translation helpful? Give feedback.
-
Oddly, when visiting this site, I experience an overall better performance with fastcompmgr as opposed to picom. But to answer your question, fastcompmgr, just like the original xcompmgr, currently has no specific means to get rid of tearing. If people continue on requesting that feature I might do so in the future 🙂. |
Beta Was this translation helpful? Give feedback.
-
I was able to get rid of the tearing by launching xorg with the Now I can use this compositor, here is a benchmark showing the cpu usage while moving a window around: If the test was right that would be a 20% reduction in cpu usage between the two, interesting. |
Beta Was this translation helpful? Give feedback.
-
Ah, ok, so you mean you have an intel graphics card and use intel's old xserver-xorg-video-intel driver? Is this
|
Beta Was this translation helpful? Give feedback.
-
Since the early days of compton, every new release made my desktop feel somewhat slower; picom, unfortunately, continues this sad tradition. That's why I travelled back in time to an early version of compton (which added shadows on argb windows), cherry picked some later compton commits to get rid of spurious segfaults and memleaks, and made that version even faster, based on profiling. Since then moving and resizing windows or scrolling complex web pages is finally smooth again. You may want check it out here: https://github.com/tycho-kirchner/fastcompmgr.
CPU usages by compositor:
Beta Was this translation helpful? Give feedback.
All reactions