Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Difference between the clock cycle and execution packet?

0
Posted

Difference between the clock cycle and execution packet?

0

With “clock” as the measurement option (Profiler-> Clock Setup->Count) you will get the actual clock cycles taken to execute your range of code. With “Execution Packet”, you get the number of execute packets it executes in that range. It is correct that in one clock cycle one Execute Packet gets executed. But apart from executing the execute packet the processor has to fetch the instructions, which is the reason for the difference in the values shown by the profiler. The statistics shown with the measurement option as “clock” will be greater than the statistics shown from the measurement option as “Execution Packet”. Enabling the cache will reduce the difference.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123