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

[Andreas Pakulat]

Hi,

On Fri, Dec 20, 2013 at 1:02 AM, Milian Wolff <mail at milianw.de> wrote:

> On Friday 20 December 2013 00:56:14 Andreas Pakulat wrote:
> > Hi,
> >
> > On Thu, Dec 19, 2013 at 8:53 PM, Michael George Hart <
> >
> > michael.george.hart at gmail.com> wrote:
> > > Kdevelop4 4.3 and 4.6 runs like a pig  on AMD Athlon(tm) XP 3200+ with
> 1
> > > GB of RAM
> > > How do I go about bringing up kdevelop4 is it most basic form
> > > so I can use the environment do some debugging?
> >
> > How about using something a bit less memory hungry that also has a decent
> > debugger like Qt-Creator?
>
> Considering the substantial effort I put into memory optimizations, I'd
> also
> be interested in knowing how QtCreator and KDevelop compare for some
> projects.
>
> Also, you can try out the sharedurls branches of KDevplatform and KDevelop,
> which will save you some megabytes of memory.
>

Well, maybe I was a bit hasty with my suggestion. My QtCreator instance
took up 641M, was running for probably 3 or 4 weeks now and being heavily
used in that timeframe (just 1 project but non-trivial, c++ and JS).

Doing the 'how big is it after startup' test for KDevelop and QtCreator.
Both load the same codebase and in both cases I've got a couple of files
open (not exactly the same but should still match up quite ok) and of
course I let the initial reparse/update run before checking. KDevelop takes
up 184M right after the parse is finished but while writing this mail and
KDevelop not being used for anything it took another 80M. QtCreator still
sits there at a 174M ever since it started and loaded its session. Since I
had to open the file in KDevelop I also noticed that opening the 5 files (4
c++, 1 js, one of them quite a bit bigger with 5000 lines) caused KDevelop
to go from 139 to the 184M.

Memory taken from KDE's process monitor (forgot the name already).

Andreas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20131220/08b6c2f8/attachment.html>