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

List:       kde-devel
Subject:    Re: KDE speed issues
From:       David Faure <david () mandrakesoft ! com>
Date:       2002-01-21 17:41:42
[Download RAW message or body]

On Monday 21 January 2002 18:22, you wrote:
> On Mon, Jan 21, 2002 at 06:01:39PM +0100, David Faure wrote:
> > How so ? We were using nana in KDE at some point (pre-2.0)
> > and it seemed to be mostly about assertions and debug output IIRC...
> > Does it have additional stuff for performance checking ?
> 
> Yup, see the above url :)
> (its the exact page for performance stuff - 
> very simple and fast timer and logging -

It associates events with times ?
Looks quite like what I just added to kdDebug locally, printing the current time in \
each kdDebug call ;)

Index: kdebug.cpp
===================================================================
RCS file: /home/kde/kdelibs/kdecore/kdebug.cpp,v
retrieving revision 1.108
diff -u -p -r1.108 kdebug.cpp
--- kdebug.cpp  2001/12/30 23:58:46     1.108
+++ kdebug.cpp  2002/01/21 17:40:26
@@ -37,6 +37,7 @@
 #include <qmessagebox.h>
 #include <klocale.h>
 #include <qfile.h>
+#include <qdatetime.h>
 #include <qintdict.h>
 #include <qstring.h>
 #include <qtextstream.h>
@@ -275,6 +276,9 @@ static void kDebugBackend( unsigned shor
                   output = stderr;
               // Uncomment this to get the pid of the app in the output (useful for \
                e.g. kioslaves)
              // if ( !aAreaName.isEmpty() ) fprintf( output, "%d %s: ", \
(int)getpid(), aAreaName.ascii() ); +             //if ( !aAreaName.isEmpty() ) \
fprintf( output, "%s: ", aAreaName.ascii() ); +              QTime cur = \
QTime::currentTime(); +             fprintf( output, "%d:%d:%d:%d ", cur.hour(), \
                cur.minute(), cur.second(), cur.msec() );
              if ( !aAreaName.isEmpty() ) fprintf( output, "%s: ", aAreaName.ascii() \
);  fputs(  data, output);
              break;

Haven't had time to use this for tuning yet, it was mainly to understand 
a timing problem in kio_ftp. However it could be used for performance
analysis too, adding kdDebug calls at the right places.

> but alas, limited overall statistics..)

Same problem ;)
 
-- 
David FAURE, david@mandrakesoft.com, faure@kde.org
http://people.mandrakesoft.com/~david, http://www.konqueror.org
KDE 3.0: Konquering the Desktops

 
> > Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


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