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

List:       kde-active
Subject:    Re: fun and profiling
From:       "Aaron J. Seigo" <aseigo () kde ! org>
Date:       2011-10-30 0:12:33
Message-ID: 10025120.2P4BhzIfBB () freedom
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Saturday, October 29, 2011 14:09:04 Marco Martin wrote:
> Hi all,
> 
> there are some things that can be evident pretty quickly with some
> profilers: i ran plasma-device in valgrind, with both callgrind, to see
> what are the functions that weight more during the startup
> and with massif, to see where all memory goes (said once again, avoid to
> even look at what top or system monitor say about the memory, is just
> misleading
> :p).
> 
> kcachegrind for callgrind and the new massif visualizer by Milian of
> Kdevelop fame can visualize it in a very very clear way, especially when
> there is one thing that eats all.

nice work :)

> the panels will look empty for an instant when opened and will kinda suck,
> but the gain is really too big ;)

they could be loaded directly after start up is complete to prevent this in 
the common case?

> * could also be tried delaying framesvg data loading by some seconds.. it
> would drive to have something visible before, but looking broken for a while
> (kinda loading of a site, maybe not too nice :p) but seems -really-
> overkill

yes, probably not worth it. startup is relatively rare and it is more 
important to look correct than start fast.

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Development Frameworks

["signature.asc" (application/pgp-signature)]

_______________________________________________
Active mailing list
Active@kde.org
https://mail.kde.org/mailman/listinfo/active


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