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

List:       kde-devel
Subject:    Re: Tools to find application bottlenecks?
From:       Lubos Lunak <l.lunak () sh ! cvut ! cz>
Date:       2002-05-21 7:03:04
[Download RAW message or body]

On Tuesday 21 May 2002 08:36, David Faure wrote:
> On Tuesday 21 May 2002 00:21, David Leimbach wrote:
> > Any profiler worth anything should do the same thing.  Gprof is one.
>
> But AFAIK is requires to compile as static, which isn't really possible in
> non-trivial KDE apps (kioslaves, kparts, etc.)
> I'd love to be told how to profile e.g. kword, but compiling static isn't
> an option I'm afraid.

 And moreover gprof doesn't provide very useful data anyway. KDE apps often 
use many small functions and in such cases the overhead of gprof can be even 
more than 2/3 . I tried few times to profile something with gprof, but I 
usually didn't manage to get very useful results (the only useful result I 
got was the malloc problem, and it was only because the slowndown in malloc 
was huge and it was located in few functions).
 I've heard there's a profiler called oprofile which used hardware support to 
collect the data and gives more useful results, I haven't tried to myself yet 
though. Still, with the way the flow path is often scattered over so many 
little places, it may be a bit difficult to analyze and interpret the results 
even with a good profiler.

-- 
 Lubos Lunak
 l.lunak@email.cz ; l.lunak@kde.org
 http://dforce.sh.cvut.cz/~seli

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