|
From: Hynek S. <hs+...@ox...> - 2006-08-13 17:18:37
|
Hi, I'm profiling software using Callgrind and as I have some rather strange results, I'd like to ask some questions to go for sure... I understand, that callgrind counts "instructions". Does it mean, that it simply adds up assembler instructions and uses it as the costs? I ask because it seems as a strange metric to me because some instructions take longer than others. This would explain, why pthread_mutex_lock() seems to hog the most costs and memcpy() (which gprof indentified as the major hog) is only neglectable. Or am I missing something here? I'd really like to understand, why Callgrind's and gprof's (and OProfile's btw, but that's not useful for me as it's granularity is too low) results differ. I couldn't find anything about this neither in the Valgrind manual nor on the KCachegrind pages, so I hope that someone here can help me... TIA, -hs |