tdesdk

History

Timothy Pearson f6940565c7 Rename additional instances of KDE to TDE		13 years ago
..
converters	TQt4 convert kdesdk	14 years ago
kcachegrind	Rename additional instances of KDE to TDE	13 years ago
pics	Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features.	15 years ago
tests	Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features.	15 years ago
AUTHORS	Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features.	15 years ago
COPYING	Fixed remaining GPL address zip codes	15 years ago
ChangeLog	Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features.	15 years ago
INSTALL	Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features.	15 years ago
Makefile.am	Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features.	15 years ago
NEWS	Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features.	15 years ago
README	Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features.	15 years ago
TODO	Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features.	15 years ago
configure.in.in	Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features.	15 years ago
kcachegrind.lsm.in	Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features.	15 years ago
kcachegrind.spec.in	rename the following methods:	13 years ago
version.h.in	Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features.	15 years ago

README

KCachegrind
===========


What is all this about ?
-------------------------

Profiling, i.e. determinating most time consuming execution parts,
is an important last step when developing applications.
KCachegrind visualizes traces, generated by profiling, in various ways;  
most notable is the TreeMap visualization of the calls happening
and a condensed version of it, the Coverage analysis.
KCachegrind is designed to allow fast browsing and to provide a quick
overview of very large programs, such as KDE applications (but not
limited to!). 
  
At the moment, it uses Cachegrind as profiling backend, which is using
the excellent CPU simulator in Valgrind. Thus, profiling does not 
need any preparation, can cope with shared libraries and plugin
architectures, and allows for profile runs to not influence the measuring
by the profile itself (all in contrast to e.g. GProf). Disadvantage is 
slower profile runs, unfortunately. 
 
For Cachegrind to provide call tree information, a patch is provided.  
This enables the most interesting visualization features of KCachegrind. 


Requirements
------------

A call-tree version of Cachegrind:
  - X86 Linux
  - Valgrind 1.0.x with call-tree patch from KCachegrind Website
  - Valgrind 2.0.x with call-tree skin installed

Cachegrind runs on x86 platforms, KCachegrind on all KDE enabled
platforms (KDE 3.0.x). 


Compilation and Installation
----------------------------

Simple do the command sequence

  ./configure --prefix=<KDE base directory>
  make
  make install



KCachegrind features
--------------------

Most important: TreeMap calltree visualisation.
For the rest, see the detailed "What's this?" help for
each part of KCachegrind and the quick starter on the
WWW page ( http://kcachegrind.sourceforge.net/cgi-bin/show.cgi )



Happy Profiling,
 Josef Weidendorfer