Skip to content

Sort benchmark numbers vary wildly across Arm64 devices #73315

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
AndyAyersMS opened this issue Aug 3, 2022 · 2 comments
Open

Sort benchmark numbers vary wildly across Arm64 devices #73315

AndyAyersMS opened this issue Aug 3, 2022 · 2 comments
Labels
area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI tenet-performance-benchmarks Issue from performance benchmark
Milestone
Future

Comments

@AndyAyersMS
Copy link
Member

AndyAyersMS commented Aug 3, 2022 •
edited by BruceForstall
Loading

See #71214 (comment)

Numbers on the Ampere are 3x that of my local dev box, which seems wrong. Also, windows/linux ampere numbers are also quite different. Seems likely the benchmark is not reliably reaching Tier1 code and so is measuring something different than one might expect.

May be difficult to make progress here until profiling issues are sorted, see #72578 and #71786

category:performance
theme:benchmarks
@ghost
Copy link

ghost commented Aug 3, 2022

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@ghost ghost added the untriaged New issue has not been triaged by the area owner label Aug 3, 2022
@AndyAyersMS AndyAyersMS added this to the Future milestone Aug 3, 2022
@ghost ghost removed the untriaged New issue has not been triaged by the area owner label Aug 3, 2022
@AndyAyersMS AndyAyersMS mentioned this issue Aug 3, 2022
Closed
@AndyAyersMS AndyAyersMS added area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI tenet-performance-benchmarks Issue from performance benchmark labels Aug 3, 2022
@ghost
Copy link

ghost commented Aug 3, 2022

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

Issue Details

See #71214 (comment)

Numbers on the Ampere are 3x that of my local dev box, which seems wrong. Also, windows/linux ampere numbers are also quite different. Seems likely the benchmark is not reliably reaching Tier1 code and so is measuring something different than one might expect.

May be difficult to make progress here until profiling issues are sorted, see #72578 and #71786

Author: AndyAyersMS
Assignees: -
Labels:

area-CodeGen-coreclr
Milestone: Future

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI tenet-performance-benchmarks Issue from performance benchmark
Projects
None yet
Milestone
Future
Development

No branches or pull requests
1 participant
@AndyAyersMS