-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[Performance] Startup regression #87235
Comments
Seems like arm64 is not affected |
@EgorBo you are correct, was checking and the last run is past the culprit build on these machines too. |
Methods jitted
|
Is there an easy way to get a list of functions that are now jitted that weren't before? |
I had done the r2rdump check for corelib as part of the PR and hadn't seen any differences; but maybe I had done something wrong here... |
should do the trick |
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsSmallest commits set: Crank command lines:
|
I guess it makes sense to add a smoke test to dotnet/sdk to e.g. check number of entries in JitDisasmSummary for a hello word. E.g if we see, say, more than 100 (the ETW thing)t hen something went wrong |
Looks like we're still jitting more methods than before. This looks to be because ASP.NET Core is using a crossgen2 version that has the issue. Once it pulls in an updated version of the SDK with the fix it should be resolved.
|
Smallest commits set:
fe98008...10222f9
Crank command lines:
The text was updated successfully, but these errors were encountered: