Skip to content

Investigate parallelizing dotnet.[js|wasm] downloads #18898

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

Closed
pranavkm opened this issue Feb 8, 2020 · 6 comments
Closed

Investigate parallelizing dotnet.[js|wasm] downloads #18898

pranavkm opened this issue Feb 8, 2020 · 6 comments
Assignees
Labels
area-blazor Includes: Blazor, Razor Components bug This issue describes a behavior which is not expected - a bug. Done This issue has been fixed feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly

Comments

@pranavkm
Copy link
Contributor

pranavkm commented Feb 8, 2020

image

@pranavkm
Copy link
Contributor Author

pranavkm commented Feb 8, 2020

Remember what this picture means.

@pranavkm pranavkm added area-blazor Includes: Blazor, Razor Components feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly labels Feb 8, 2020
@rynowak
Copy link
Member

rynowak commented Feb 8, 2020

OK. I will. Thanks :)

@javiercn
Copy link
Member

@pranavkm We plan to do this with link rel=preload

@pranavkm
Copy link
Contributor Author

@javiercn is there an issue we can duplicate this with in that case?

@SteveSandersonMS
Copy link
Member

Seems super basic to do just by moving a few lines of .ts code: #20029. Result:

image

The highlighted block contains all requests for .dll, .pdb, .wasm, and dotnet.*.js, and they all start loading at roughly the beginning of that block.

@SteveSandersonMS
Copy link
Member

Fixed in #20029

@SteveSandersonMS SteveSandersonMS added the Done This issue has been fixed label Mar 20, 2020
ghost pushed a commit that referenced this issue Mar 25, 2020
* Restore public API contract on WebAssemblyJSRuntime (#19968)

* Shrink icon-512.png (#19999)

* Use custom DebugProxyHost to initialize DebugProxy config (#19980)

Addresses #19909

* Spruce up WebAssemblyHostEnvironment interface and use (#20008)

* Load .dlls/.wasm/.pdb in parallel with dotnet.*.js. Fixes #18898 (#20029)

* Add BaseAddress property to WebAssemblyHostEnvironment (#20019)

- Adds `BaseAddress` to `IWebAssemblyHostEnvironment`
- Uses unmarshalled APIs to extract application host
- Move NavigationManager initialization to startup code
- Fix subdir mapping in ClientSideHostingTest

Addresses #19910

Co-authored-by: Steve Sanderson <[email protected]>
Co-authored-by: Safia Abdalla <[email protected]>
Co-authored-by: Safia Abdalla <[email protected]>
@ghost ghost locked as resolved and limited conversation to collaborators Apr 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components bug This issue describes a behavior which is not expected - a bug. Done This issue has been fixed feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly
Projects
None yet
Development

No branches or pull requests

5 participants