We, Loading Tokyo team, experimentally start sending weekly snippets.
Feel free to send any feedback.
Updates:
ES6 modules
Performance (ksakamoto, kouhei)
Ksakamoto: Module loading performance report
Kouhei: Un-webpacking airbnb to find out real-world use cases.
Dynamic imports (kouhei)
Classic script CSP test passes
Mojo-Loading
Investigated UMAs further.
The crash bcwhite@ fixed originated from M61 but we saw the crash rate difference in M60 (bad news)
I see some mojo::edk::Watcher* crashes after bcwhite@’s fix (bad news)
The difference in M60 was not observed originally. It suddenly went up around Aug 23. I found that the difference was not from Chrome version difference (event fixing the version the sudden increase is observed).
We saw a significant crash rate increase on M61 beta in Aug but the crash rate increase on M62 beta in Sep looks better even without bcwhite@’s fix (good news).
Servicification
Wrote SimpleURLLoader migration plan (kinuko@, mmenke@): doc
Redirect handling changes
Redirect handling needs to be done by multiple URLLoaderClient implementors (and also we still need it in //net)
NavigationURLLoaderNetworkService doing same/similar to what net::URLRequest::Redirect does, we also need something similar to SW subresource handling in the renderer process
Plan: will have common redirect code for all these (e.g. net::RedirectUtil::UpdateHttpHeader)
Out-of-Blink CORS
Make the WebCORSPreflightResultCache back to be thread local. (crrev.com/67d4e60)
Add spec links for fetch related enums
DocumentThreadableLoader: stop recording JS initiated non-GET fetches
WebCORS: mechanical style and comment fixes
CORSURLLoaderTest
Origin Manifest
Kick-off meeting with Munich
Design doc review
More predictable MemoryCache
As a follow-up for the discussion done in SpeedConvergence, japhet@ landed yet another patch not to retain resources if the navigation is cross-site.
hiroshige@ will help with experiment set-up
Scalable loading / 10k measurement
Wrote a doc for 10k measurement with recent perf measurement updates
Asked by Addy (for CDS etc), being also asked by FB
Waiting for ksakamoto@’s sign-off before circulating more widely
WebFonts (toyoshim)
Intervention V2 launch efforts
WebFontsIntervensionV2: experiment-controlled rollouts, step 1 (cr/170663524)
WebFontsIntervensionV2: experiment-controlled rollouts, step 2 (cr/171101260)
WebFonts intervention: remove ios from the platform list (cr/171120195)
WebFonts intervention: Enable v2 by default
WebFontsIntervensionV2: experiment-controlled rollouts, step 3
Review ExecutionContext related crash fix changes
Fetch keepalive
KeepAliveRendererForKeepaliveRequest looks good. I’ll just enable it if no one complains.
Preparing intent-to-implement.
ResourceLoadScheduler (toyoshim)
Verify if AMP works fine with our throttling
ResourceLoadScheduler: add a sub-frame specific param to limit requests (crrev.com/f2f17ad)
ResourceLoadScheduler: update configurations to use bg_sub_limit (cr/171254049)
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFWCB1nZ%3DHWcbTCZk7rt4iJJuAMS_fCOZPfPN%3DT10zxUwxpRJQ%40mail.gmail.com.
[bcc: blink-dev, chromium-dev]
> result of measuring Module vs Bundled seems similar to MultiFile vs SingleFile for me.
> (so `Module` or `Scripts` are less influence for this result).
Yes. Looking at the current trace analysis, the current bottlenecks seem common for both {module,classic} script cases. (You can see where bottleneck comes in many-scripts/modules cases here too)
However, there are some important differences to note:
- module scripts may import other module scripts
- module scripts are compiled before being scheduled to run
> if web-packaging will packs multi modules to single file, will works fine for update Recommendation ?
Do you mean if we pack multiple modules with native format like Web Packaging it will change the situation? It’d largely depend on how it would be implemented and we don’t have a clear answer for that yet.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/loading-dev/53dd13b7-8324-41f8-90c3-d2329f905feb%40chromium.org.--
You received this message because you are subscribed to the Google Groups "loading-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to loading-dev+unsubscribe@chromium.org.
To post to this group, send email to loadi...@chromium.org.