Skip to content

[StaticWebAssets] Backport perf fixes #47913

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

Draft
wants to merge 8 commits into
base: release/9.0.3xx
Choose a base branch
from

Conversation

* Removes the usage of Microsoft.Extensions.FileSystemGlobbing in favor
  of a custom implementation optimized for our scenarios.
* Improves the parallelism in DefineStaticWebAssetEndpoints.
* Spanifies the string manipulation logic.
* Ensures that only DefineStaticWebAssets hits disk
* Avoids doing extra work on tasks that need to use the length or the last write time.
* Simplifies other tasks like DefineStaticWebAssetEndpoints and ApplyCompressionNegotiation
* Makes the task incremental and retrieves the results from a cache to avoid hitting disk to compute integrity and fingerprint on incremental builds
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-AspNetCore RazorSDK, BlazorWebAssemblySDK, dotnet-watch untriaged Request triage from a team member labels Mar 26, 2025
@javiercn javiercn changed the base branch from main to release/9.0.3xx March 26, 2025 15:00
Copy link
Contributor

Thanks for your PR, @javiercn.
To learn about the PR process and branching schedule of this repo, please take a look at the SDK PR Guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-AspNetCore RazorSDK, BlazorWebAssemblySDK, dotnet-watch untriaged Request triage from a team member
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant