4 ms·
If Cpython is transferred as a separate artifact, probably for a CDN, it will be cached super efficiently. I'm not sure whether it's that much of a problem.
by joelthelion 4y ago
If Cpython is transferred as a separate artifact, probably for a CDN, it will be cached super efficiently. I'm not sure whether it's that much of a problem.
- __alexs 4y agoBrowsers do not share cache hits to CDNs anymore. The cache is sharded (not shared) across origins.
- rewq4321 4y agoAs of quite recently that may be changing in Chromium (early experiment): https://groups.google.com/a/chromium.org/g/blink-dev/c/9xWJK3IgJb4 https://groups.google.com/a/chromium.org/g/blink-dev/c/9xWJK... IIUC, the TLDR is that they're experimenting with loading a bunch of popular scripts (e.g. top `N` scripts from CDNs) on all browsers, so the response is immediate, but they can't use the timing for fingerprinting because it's immediate for everyone.
- tlarkworthy 4y agoOf course it's a problem, that cache is not shared across domains, so it will be the initial experience of your users. Perhaps they can do some kind of lazy loading magic to hide it eventually
- asojfdowgh 4y agouncached, 8 seconds, cached, 6.5 seconds Loading the entire wasm, touching all the things that need to be touched, etc, takes up the majority of the time
- toyg 4y agoThe good thing though is: because it's a WASM problem, not a Python problem, it will likely get better with time, and the benefits will automatically percolate to Python too.