TDE
/
tdesdk
6
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
tdesdk/tdecachegrind
History
Michele Calgaro b0c86264e0
Use new TQ_METHOD, TQ_SIGNAL, TQ_SLOT defines 		3 months ago
..
converters Removed code formatting modelines. 4 years ago
pics Fix invalid headers in PNG files and optimize for size 8 years ago
tdecachegrind Use new TQ_METHOD, TQ_SIGNAL, TQ_SLOT defines 3 months ago
tests Part 2 of prior commit 12 years ago
AUTHORS Part 2 of prior commit 12 years ago
CMakeL10n.txt Add CMakeL10n rules. 5 years ago
CMakeLists.txt Fixed FTBFS caused by previous commit (lsm files removal). 5 years ago
COPYING Part 2 of prior commit 12 years ago
ChangeLog Rename additional global TQt functions 12 years ago
ConfigureChecks.cmake [tdesdk/cmake] added forgotten files 12 years ago
INSTALL Part 2 of prior commit 12 years ago
Makefile.am Fixed FTBFS caused by previous commit (lsm files removal). 5 years ago
NEWS Part 2 of prior commit 12 years ago
README Branding cleanup: KDE -> TDE. 12 years ago
TODO Rename a number of classes to enhance compatibility with KDE4 11 years ago
configure.in.in Fixed FTBFS caused by previous commit (lsm files removal). 5 years ago
tdecachegrind.spec.in Part 2 of prior commit 12 years ago
version.h.in Part 2 of prior commit 12 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 TDE 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://tdecachegrind.sourceforge.net/cgi-bin/show.cgi )



Happy Profiling,
 Josef Weidendorfer