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

Startup Performance Worse than .Net Framework 4.8 #2736

Closed
jtg15 opened this issue Mar 8, 2020 · 1 comment
Closed

Startup Performance Worse than .Net Framework 4.8 #2736

jtg15 opened this issue Mar 8, 2020 · 1 comment

Comments

@jtg15
Copy link

jtg15 commented Mar 8, 2020

.NET Core 3.1.101
Windows version 1909
Does the bug reproduce also in WPF for .NET Framework 4.8?: No

I noticed that .NET Core WPF feels noticeably more sluggish than when using .NET Framework WPF especially with startup times.

I searched around for some other issues related to performance and I found this #1549. Using the same repo here: https://github.com/rladuca/NetCorePerformanceTest, I profiled it and I screenshotted the results.

perfNetLeftCoreRight

The .NET Core app is using about 2-3x more CPU time on startup and from my measurements it is taking about 400-500ms more to show the window. The render time seems to have been fixed but startup/construction time still seems to have regressed significantly.

With an empty WPF project on .NET Core and .NET Framework the results are similar.

2020-03-08 (2)

@jtg15 jtg15 changed the title Startup Performance Worse than .Net Frameworrk Startup Performance Worse than .Net Framework Mar 8, 2020
@jtg15 jtg15 changed the title Startup Performance Worse than .Net Framework Startup Performance Worse than .Net Framework 4.8 Mar 8, 2020
@rladuca
Copy link
Member

rladuca commented Mar 10, 2020

This is a function of the difference between ngen and ReadyToRun/crossgen. We already have a tracking bug in WPF (#1748) for this and a companion bug here: dotnet/runtime#13339.

I'm going to close this as a duplicate, please add your comments and upvotes to the dotnet/runtime bug.

@rladuca rladuca closed this as completed Mar 10, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Apr 12, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants