Skip to content
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.

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

JIT: remove size contribution to perf score #97069

Merged
merged 5 commits into from
Jan 19, 2024

Conversation

AndyAyersMS
Copy link
Member

Keep the perf score a pure performance metric. Size is emitted as a separate metric, so clients interested in a metric that is some combination of size and speed can do their own computations based on these two values.

Resolves #96878.

Keep the perf score a pure performance metric. Size is emitted as a separate
metric, so clients interested in a metric that is some combination of size
and speed can do their own computations based on these two values.

Resolves dotnet#96878.
@dotnet-issue-labeler dotnet-issue-labeler bot added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label Jan 17, 2024
@ghost ghost assigned AndyAyersMS Jan 17, 2024
@ghost
Copy link

ghost commented Jan 17, 2024

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

Issue Details

Keep the perf score a pure performance metric. Size is emitted as a separate metric, so clients interested in a metric that is some combination of size and speed can do their own computations based on these two values.

Resolves #96878.

Author: AndyAyersMS
Assignees: -
Labels:

area-CodeGen-coreclr

Milestone: -

@AndyAyersMS
Copy link
Member Author

@dotnet/jit-contrib FYI
@jakobbotsch PTAL

Comment on lines -2008 to -2010
compiler->info.compPerfScore += ((double)compiler->info.compTotalHotCodeSize * (double)PERFSCORE_CODESIZE_COST_HOT);
compiler->info.compPerfScore +=
((double)compiler->info.compTotalColdCodeSize * (double)PERFSCORE_CODESIZE_COST_COLD);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should remove the definitions of PERFSCORE_CODESIZE_COST_HOT / PERFSCORE_CODESIZE_COST_COLD, which will be no longer used.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks, done.

@BruceForstall
Copy link
Member

Odd the CI never ran anything...

@AndyAyersMS
Copy link
Member Author

NAOT failure was #94728.

@AndyAyersMS AndyAyersMS merged commit 24f9706 into dotnet:main Jan 19, 2024
125 of 129 checks passed
tmds pushed a commit to tmds/runtime that referenced this pull request Jan 23, 2024
Keep the perf score a pure performance metric. Size is emitted as a separate
metric, so clients interested in a metric that is some combination of size
and speed can do their own computations based on these two values.

Resolves dotnet#96878.
@github-actions github-actions bot locked and limited conversation to collaborators Feb 19, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[JIT] PerfScore includes code size impact?
3 participants