I'm confused here. Does this core path only run once per second? I've had no problems profiling blocks of code that short, because it sounds like every inner lo

I'm confused here. Does this core path only run once per second? I've had no problems profiling blocks of code that short, because it sounds like every inner loop to me. If you're looking to optimize a few hundred instructions, then focus on reading and understanding the code manually at the instruction level. A profiler will never help you there, CPUs are too complex: 1. I don't trust that the profiler has equal probability of pausing on any specific instruction 2. CPUs do no execute instructions in sequence, but in parallel. So you will need to understand data dependencies & maybe pipeline structures for your target processor. If you're getting really serious, you'll want something like https://uops.info/table.html https://uops.info/table.html