[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: KDE4 is a memory hog
From:       dunsens () web ! de
Date:       2009-07-17 11:28:58
Message-ID: 200907171328.58875.dunsens () web ! de
[Download RAW message or body]

Am Freitag, 17. Juli 2009 schrieb Carlo:
> On Fri, Jul 17, 2009 at 11:45 AM, <dunsens@web.de> wrote:
> > Hi,
> >
> > I have now tried, stepped ahead and installed 4.2.4 on my machines
> > (debian- desktop.org backports). I have to say that I am quite pleased.
> > Since the PS3 has a fast swap it is actually capable of running KDE4
> > sessions. The C3 feels slow, but 512mb seem enough. KWin crashes with my
> > default settings for openchrome via driver though, so i had to disable
> > the composite extension. The PS3 feels a bit sluggish, but it does not
> > really get in your way. You can run Kopete + Firefox + amarok (1.4). This
> > is really o.k. (No youtube of course, shame at adobe).
> > I can also login 3 sessions with an typical work environment on the 1gb
> > ram machines. I get 100-200mb swapping then, but I guess that 4.3 will
> > improve that due to the nvidia issue.
> >
> > Things that I have seen testing with exmap/valgrind --massif:
> >
> > -Fonts can make a huge difference. Parts of my high memory usage seem to
> > be related to using "Free Sans". I am at DejaVu Sans now and it is
> > better. Dolphin shows high heap usage related to libfreetype for example.
> > But it is not really gone - Konsole uses 7mb heap for a one bash tab:
> > 91.09% (6,792,796B) (heap allocation functions) malloc/new/new[],
> > --alloc-fns, etc.
> > ->44.73% (3,335,865B) 0x5CCDCEC: (within /usr/lib/libfreetype.so.6.3.18)
> >
> > | ->44.73% (3,335,865B) 0x5CD1EBA: ft_mem_qalloc (in
> >
> > /usr/lib/libfreetype.so.6.3.18)
> >
> > |   ->44.73% (3,335,865B) 0x5CD3B72: ft_mem_alloc (in
> >
> > /usr/lib/libfreetype.so.6.3.18)
> >
> > -Konqueror really is a memory hog although it seems to not be. It uses
> > more memory on the same three tabs/sites test setup than firefox,
> > although exmap even calculates the shared lib usage where it should have
> > a great advantage. This is bad since Firefox has not nearly a as good kde
> > integration.
> >
> > -Kopete takes too much memory. It has a total memory of between 20-24mb
> > here, having 12mb heap:
> > 85.80% (10,692,856B) (heap allocation functions) malloc/new/new[],
> > --alloc- fns, etc.
> > ->24.69% (3,077,240B) 0x4F67DCC: qMalloc(unsigned) (in
> > /usr/lib/libQtCore.so.4.4.3)
> >
> > | ->07.87% (981,434B) 0x4FB1AB8: QString::realloc(int) (in
> >
> > /usr/lib/libQtCore.so.4.4.3)
> > Don't know why, but I guess that could be better... Maybe it is due to
> > the emoticons being cached...
> >
> > -Akonadi takes round about 30 mb. I just kill it if I need to. The always
> > on startup message about migrating the standard ressources gets on my
> > nerves, too, btw....
> >
> > -Amarok really uses between 60-70 mb on kubuntu here. This does not mean
> > much as heaps seem to be generally larger on kubuntu for some reason. But
> > 70 mb is really bad.
> >
> > I am happy to be able to use KDE4 on my systems now and I am looking
> > forward to use 4.3/4.4. It is really the most advanced *nix desktop imo,
> > so thx for your great work!
> >
> > Cheers,
> > whilo
>
> the PS3 is slugghish because there are just 256mb of ram, and you
> can't use the SPEs for general purpose, so it's just a single core PPE
> with something like hyper threading
it is even less. it is only round about 200mb. it still works. and you can now 
use the graphics memory as a fast swap space, which i do. so you can use it. 
you are right about cpu power though... hopefully the spes will work for 
graphics acceleration sometime in the future. but I'm ok with the current 
situation. 
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> >> unsubscribe <<


-- 
My blog: http://whilos.blogsite.org

No brain - no headache!
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]