-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[browser] app start benchmark fix, loadBootResource fix #89857
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
Conversation
- use noCache and useCredentials flags on asset just for appsettings configuration, not all VFS - delay cache cleanup 10 seconds later - delay adding new cache items to timer loop - replace ResourceRequest usage with AssetEntryInternal - remove ResourceRequest type
|
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsAs we introduced cache also for non-blazor template, we also adopted it's resources cache and
|
Co-authored-by: Ankit Jain <[email protected]>
Co-authored-by: Ankit Jain <[email protected]>
- minor importLibraryInitializers refactoring
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
As we introduced cache also for non-blazor template, we also adopted it's resources cache and
no-cachehint forfetch.Because our SimpleServer which we use for benchmark doesn't use ETag header, it leads to full download.
loadBootResourcetoo earlydotnetwasmlocation before cache lookup #89883ETagHTTP header forSimpleServerand benchmarkdisableNoCacheFetchanddisableIntegrityCheckconfig flagsnoCacheanduseCredentialsflags on asset just for appsettings configuration, not all VFSResourceRequestusage withAssetEntryInternalResourceRequesttypejs-module-library-initializerandmanifestimportLibraryInitializersrefactoring