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

Michael George Hart michael.george.hart at gmail.com
Fri Dec 20 20:47:28 GMT 2013


kdevelop -graphicssystem native

The performance is GREAT!!!!!!!!
Even with every feature turned on in kdevelop4

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.

I looked at --help-qt and did not see any mention about the option "native"
for "-graphicssystem"
I only saw "--graphicssystem <system> use a different graphics system
instead of the default one, options are raster and opengl (experimental)"
My question is why would I every want raster... it seems wastefully use of

Thanks!!! Now, if I only could figure out to use kdevelop4 effectively for
remote development and debugging against hardware different from my host,
like a 32 bit linux system, I would be in pigs heaven.

Thanks again

On Fri, Dec 20, 2013 at 2:36 PM, Sven Brauch <svenbrauch at googlemail.com>wrote:

> Oh you run it *remotely*.
> Maybe it would have made sense to mention that a bit earlier, because
> it is very relevant.
> Qt4 now by default uses a raster graphicssystem which draws images
> into pixmaps and the draws the pixmaps on the screen. That is very
> slow via X11 forwarding. Use kdevelop -graphicssystem native to get
> back to the old variant.
> Greetings,
> Sven
> 2013/12/20 Michael George Hart <michael.george.hart at gmail.com>:
> > Well, I am kind of stubborn and made on last ditch effort.
> > and totally erased the .kde4 directory that was remotely logging onto
> >
> > installed a fresh copy of kdevelop4 then tuned off word completion,
> > background parsing etc.
> >
> > Relative to Kdevelop3 it was sluggish but now usable.  From what I can
> > observed I can only guess the major source of my is GUI element that
> > comprise kdevelop4. As long as I kept the total window size of kdevelop4
> > less than 2/3 the resolution of 1200x1600 the system was sluggish but
> > usable.
> >
> > The reason I think the problem is directly related to the GUI elements
> in 4
> > is a simply act of trying to resize the 4's windows size can take up to
> five
> > to ten seconds; the mouse moves then about 5 seconds later the window
> > resizes to the mouse position; then a few seconds later everything
> settles
> > down and I can start editing again; like tons of network traffic just to
> > resize a kdevelop4 window; this does not happen with kdevelop3 or
> dolphin,
> > konqueror ....
> >
> > That is my WAS :)
> >
> > But it is usable.
> >
> >
> > On Fri, Dec 20, 2013 at 1:45 PM, Sven Brauch <svenbrauch at googlemail.com>
> > wrote:
> >>
> >> > I am left with few other options under the time constraints I am
> under.
> >> Well, I'm not sure what you expect to happen. If you want anyone to
> >> help, provide some useful information instead of complaining about the
> >> program's design. You're just here grumping about everything but you
> >> didn't even tell us how much RAM it actually uses.
> >>
> >> Sven
> >
> >
> >
> >
> > --
> > "...Hope is what makes us strong. It is why we are here. It is what we
> fight
> > with when all is lost..."

*"...Hope is what makes us strong. It is why we are here. It is what we
fight with when all is lost..."*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop/attachments/20131220/79c30dd9/attachment.html>

More information about the KDevelop mailing list