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.

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

Investigate loading ReadyToRun version of Roslyn in ConfigurationSchemaGenerator #1426

Open
eerhardt opened this issue Dec 16, 2023 · 0 comments
Open

Investigate loading ReadyToRun version of Roslyn in ConfigurationSchemaGenerator #1426

eerhardt opened this issue Dec 16, 2023 · 0 comments
Labels
area-integrations Issues pertaining to Aspire Integrations packages
Milestone
future (would tak...

Comments

@eerhardt
Copy link
Member

Performance wise, the tool takes ~400-500 ms to run. An option we should try is to load the Roslyn assemblies from the SDK, which are already R2R'd. This may make the tool faster because it won't need to JIT Roslyn every time it is run. This would be the same logic used in dotnet/sdk#22277.

We should try this and see if it makes a measurable difference in how long it takes to run.
@eerhardt eerhardt added the area-integrations Issues pertaining to Aspire Integrations packages label Dec 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-integrations Issues pertaining to Aspire Integrations packages
Projects
None yet
Milestone
future (would take a change but work ...
Development

No branches or pull requests
1 participant
@eerhardt