Fixed a bug on example code at 5.6. Getting Accurate Results #321
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@lshqqytiger benchmarked the example codes on ThunderX2 CN9980 processor, but the performance did not meet our expectations.
Interestingly, Case 2 performed faster than Case 1.
Case 1 took 0.104947 seconds, while Case 2 took 0.075065 seconds.
The faster speed of Case 2 was due to a high branch prediction rate. In Case 2, there were only 1,000 combinations of
gcd
arguments, enabling the branch predictor to memorize the entire sequence of comparison and perform branch prediction successfully.To ensure the example code executes 1 million combinations of
gcd
arguments as intended, I modified the code as follows:Case 3 took 0.122731 seconds, performing the expected result.