Hi,
I'm attempting to profile (the memory usage and CPU time of) some code
I've written as part of a custom datatype. I've attempted to utilise
valgrind and cachegrind, but this doesn't seem to work as expected. The
following is the command used:
valgrind --tool=cachegrind
William Harrower wjh...@doc.ic.ac.uk writes:
Ignoring valgrind specifically, does anyone know of any other tools that
can be used to profile the memory usage and CPU time/load of a custom
datatype library?
oprofile on recent Fedora (and probably other Linux distros) pretty much
just works
