Preparing For The Release of Wayland 1.0

[Sidicas]

http://www.phoronix.com/scan.php?pag...desktops&num=6
There is comparison of KDE with and without compositing.
Applications are much faster if compositing is disabled.

That's not really true. "Suspended" is not the same as "Disabled". KWIN can be "enabled" and set to auto-suspend when a full screen application starts, and it works flawlessly so KWIN doesn't sap performance from your video card.

There are at least two major benefits that KWIN can do that can significantly increase your desktop experience on slower, older hardware.

The first one is "scale resize" effect. This allows you to GPU accelerate resize any window and it will resize the window with perfect smoothness. If you turn this off, resizing a firefox window with a modern webpage loaded inside it is very choppy on my PC. This desktop effect is *amazing* as the CPU usage while resizing windows drops to 0% instead of 100% and it is *very* smooth on a 6+ year old laptop.

The other major benefit that KWIN compositing can do is fix the repainting problems where you move a window in front of another window. The CPU is too busy to redraw the other window so you see a messy trail of the first window all over the second window. At least until the second window gets a chance to redraw. So you get presented with an incorrect display of your open applications. With KWIN Effects enabled, this simply never happens anymore and you can drag windows wherever you like without having any window trail problems.

So yes, even though I'm running kwin effects with only 1 desktop effect, I'd definitely say that my Desktop is a lot better because of it. Also, I can confidently say my Desktop is better than Windows XP as I know the "window trailing" in front of other windows that "aren't responding" was always an annoying graphical problem on Windows XP.

Further, I can force my GPU into a low power state and KWIN still runs smoothly.

[JS987]

Does Wayland support XRender?

[freedam]

Please, take a look (and read) here: http://wayland.freedesktop.org/architecture.html, there is a big architectural difference between a Wayland compositor and a X compositor, Weston isn't "yet another X compositor".

[JS987]

Hint: XFCE, KDE and GNOME3 also use compositing and are still faster than Unity. You should read a little bit more not just look at some graphs.

http://www.phoronix.com/scan.php?page=article&item=ubuntu_1210beta_desktops&num=6

There is comparison of KDE with and without compositing.
Applications are much faster if compositing is disabled.

[oneman]

http://media.kradradio.com/files/Wayland/wl_top_tunes30p_hi.webm

https://github.com/soreau

[blackout23]

According to most benchmarks at Phoronix compositing slows down OpenGL applications.

Hint: XFCE, KDE and GNOME3 also use compositing and are still faster than Unity. You should read a little bit more not just look at some graphs.

[JS987]

Care to explain why compositing in general is a bad thing and why it should be inherently slow?

According to most benchmarks at Phoronix compositing slows down OpenGL applications.

[blackout23]

It doesn't matter how compositor is named.

Care to explain why compositing in general is a bad thing and why it should be inherently slow?

[freedam]

It isn't a matter of names, the things that you posted were meaningless...

[JS987]

lol if anything then Weston is similar to Compiz (being a compositor as an example implementation of the Wayland Protocol). The fact that you can't even make this distinction leads me to belive, that you don't know much about the whole issue.

It doesn't matter how compositor is named.