Re: Profiller for Linux
- From: Noob <root@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 24 Mar 2008 12:34:13 +0100
gpderetta wrote:
Noob wrote:
LinuxAsm wrote:
Does anyone know of a good code profiler for Linux?
I recommend oprofile over gprof.
http://oprofile.sourceforge.net/about/
Valgrind is extremely good for doing both source level
and assembler level profiling (you get execution count
for every single instruction!).
It also does cache (both data and instruction) and memory
allocation profiling.
Kcachegrind is the perfect companion for examining and
navigating valgrind output.
The downside of valgrind is that your program will run very
slowly (even 30x) when profiling. But I have found it incomparably
more useful than gprof. I have no experience with oprofile.
If a profiler is too intrusive (high overhead) then it is not profiling the application, but the combination of the application AND the profiler itself. The impact of cache misses will be incorrectly reported because the timing is different, and the profiler itself will induce extraneous data and cache misses.
cf. http://en.wikipedia.org/wiki/Observer_effect
Regards.
.
- Follow-Ups:
- Re: Profiller for Linux
- From: gpderetta
- Re: Profiller for Linux
- References:
- Profiller for Linux
- From: LinuxAsm
- Re: Profiller for Linux
- From: Noob
- Re: Profiller for Linux
- From: gpderetta
- Profiller for Linux
- Prev by Date: Re: Problem with fasm
- Next by Date: Re: Problem with fasm
- Previous by thread: Re: Profiller for Linux
- Next by thread: Re: Profiller for Linux
- Index(es):
Relevant Pages
|