C++ profiling: clock cycle count
I'm using valgrind --tool=callgrind to profile a critical part of my C++ program.
The part itself takes less that a microsecond to execute so I'm profiling over a large number of loops over that part.
I noticed that instructions take multiples of 0.13% time to execute (percentage out of program total time to execute). So I only see 0.13, 0.26, 0.52, so on.
My question is, should I assume that this atomic quantity measures a CPU cycle? See photo.
(The callgrind output is presented graphically with kcachegrind.)
Edit: By the way, looking at machine code, I see mov takes 0.13 so that's probably a clock cycle indeed.
Callgrind doesn't measure CPU time. It measures instruction reads. That's where the "Ir" term comes from. If the multiples are of .13% (especially since you confirmed with mov) then it means that they are measuring a single instruction read. There are also cache simulation options that let it measure how likely you are to have cache misses.
Note that not all instructions will take the same time to execute, so the percentages do not exactly match the amount of time spent in each section. However, it still gives you a good idea of where your program is doing the most work, and likely spending the most time.
- Which number, 0 or 1, should I define the variabliable of loops for arrays from?
- The `write` syscall in C writes to an unexpected position
- Can I dup and change the buffer behaviour of the new fd without changing the old one?
- OpenCV Error: Sizes of input arguments do not match (The operation is neither 'array op array')
- how compiler works to evaluate sizeof operator in c
- Code Fragment: is this pure C?
- ‘struct' declared inside parameter list
- Can time(NULL) ever return failure?
- Format specifier in scanf for bool datatype in C
- What does %[^\n] mean in C?
- What does it mean by `-fno-signed-char, --signed-char` for gcc & clang?
- How can embedded systems be elegantly compatible with 32-bit and 64-bit timestamp content printing?
- Specifying size of enum type in C
- Graphical user interface Tutorial in C
- gcc arm optimizes away parameters before System Call
- ARM V7 inline assembly - moving a C variable into a register
- How to fix "pointer ‘old’ may be used after ‘realloc’ [-Wuse-after-free]" warning in C?
- Why is an empty integer array filled with seemingly garbage data in C?
- Confusion of virtual memory
- Variable address does not fall within the stack range in /proc/self/maps
- Why does carg(-0) return -pi?
- To the power of in C?
- How do you do exponentiation in C?
- Will this be a tail call or not?
- Calculating a catalan number in C
- Why is the '&' operator needed for an int variable but not for an array in C?
- populating an array at compile time in C
- Why is the initialization of this structure global variable wrong?
- Efficient linked list design for a C file manager
- Function with a malloc on a pointer declared in main()