Kdevelop4 4.3 and 4.6 runs like a pig on AMD Athlon(tm) XP 3200+

Sven Brauch svenbrauch at googlemail.com
Fri Dec 20 21:18:28 GMT 2013


> This should be the first thing in your documentation for us system level non
> GUI people. --We tend to do development over a network on a piece for a
> particular hardware environment.
Well, if you google "kdevelop x11 forwarding" first thing you find is
this https://bugs.kde.org/show_bug.cgi?id=293587 which has the
solution ;)

> My question is why would I every want raster... it seems wastefully use of
> resources
It's not; I'm fairly certain it has better performance on local
screens than the native one. Additionally, it is more portable
(doesn't depend on X11).
The problem is just that it combines horribly with X11 forwarding. X11
forwarding forwards the draw calls; it basically transfers the code
which draws UI elements over the network, and the actual pictures are
assembled on the other side. This has turned out to be hard to
maintain and unflexible; it is widely considered a legacy way to draw
UI elements. Thus, the more recent way for Qt to draw UI elements is
drawing them into pixel images itself, and then telling the underlying
graphics stack to just put those images onto the screen. This doesn't
work well with X11 forwarding though, since you end up sending a lot
of large, uncompressed images over the network.


More information about the KDevelop mailing list