perf: disable subgraph passthrough #208
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is another case discovered by the performance testing actually. And that is that it turns out that while Firefox and Safari seem to share their script cache with their fetch cache, they don't actually seem to do the converse in sharing the fetch cache with the module cache. As a result, when polyfilling a module graph, if any of those subgraph modules are directed to the native loader URL instead of using the blob version this results in a double fetch and causes a bandwidth slowdown.
By ensuring that in the polyfill case all subgraphs use the blob form as fetched, we avoid this slowdown. For normal module loads that aren't blobs we maintain the native registry.
A documentation note is included for polyfill mode that having some graphs as native and some being polyfilled will result in no instance sharing between these.