5 ms·

It's been found that resource concatenation is still more efficient http://engineering.khanacademy.org/posts/js-packaging-http2.htm http://engineering.khanacade

• magicalist 11y ago
  > It's been found that resource concatenation is still more efficient http://engineering.khanacademy.org/posts/js-packaging-http2....* http://engineering.khanacademy.org/posts/js-packaging-http2.... for a page with 2.4MB of JS spread over 296 files. And, notably, the article doesn't advocate for serving individual files in the first place, but instead says that some level of grouping is likely advantageous, but http2 gives new opportunities which will need to be explored, like grouping by level of churn in libraries or by units of functionality > And 'building for http2' seems to be advocating hashes in filenames without neccesarily walking the dependencies I believe you misread. They use a shallow tree in their scout js file; all of the resources a page will need are declared there and nothing is loaded in succession. > Manifest files are a bad idea, except perhaps for instructing webservers to tell browsers to preemptively download files. AFAIK there isn't a standard for this yet so a manifest doesn't solve the problem I'm not sure what this means. The manifest is generated by the build process. There is no standard for dependency manifests, sure, but there's no reason you can't whip a reasonable one up that a simple server module could understand if you wanted to add push support. Eventually the cow paths will be paved and we'll come up with a more standardized approach (or approaches) to that kind of manifest.
  • holloway 11y ago
    > for a page with 2.4MB of JS spread over 296 files. Fair point, there is always sweet spot in benchmarks like this. That said there are examples of delays that they mention which seem to be independent of the amount of requests. >> I believe you misread. They use a shallow tree in their scout js file; all of the resources a page will need are declared there Being shallow doesn't fix the problem when resources are split up at all and that's what the article (correctly) suggests to benefit from HTTP/2 features. As we move away from a single bundle.js file we need to think more about how to manage splits. E.g. The article talks about splitting into `application` and `vendor` hashes, and you mention grouping by churn or functionality. So presumably we agree that being able to split files without significant speed loss is a major feature of HTTP/2. All I'm suggesting is that the filename hashing strategies need to be improved to avoid application errors when splitting. If we don't improve filename hashing strategies then we'd still have to rely on small HTTP cache durations, or we'd get temporary errors while caches expire, which is a problem because the whole point of the article is to have extremely long cache durations. As they say, "Files loaded by the scout can have extremely long cache times because [...]" Then as the article says, "This can be solved by using hashes of the file contents rather than version numbers: vendor-d41d8cd98f.js. If a file has not changed, its hash will remain the same." This is bad advice because they don't talk about dependencies affecting hashes. Even if that file hasn't changed but it depends on another file then its hash needs to change too, or else application.js will will have different contents depending on when it was loaded. Eg. application.js has a requirejs import of vendor.js requirejs(["vendor.js"], function(vendor){ }); So if we generated a naive hash as suggested then application-45345345345.js might look like, requirejs(["vendor-3455345ABCDFFF.js"], function(vendor){ }); Then vendor.js changes but application.js doesn't, and so application-45345345345.js is updated to read, requirejs(["vendor-f2ab4cde6f55.js"], function(vendor){ }); And now you can see the problem that application.js didn't change but it's dependencies did, so application-45345345345.js will have different data depending on when you access it which is exactly what you don't want with long HTTP cache durations. This can cause mismatches in what version of a file is imported, and cause application errors. The only way to have permanent URLs with content that doesn't change (a prerequisite for long HTTP cache durations) is to include dependencies in the calculation of filename hashes. Or you could have an dynamic resolver (eg. based on a manifest file) but ES6 and SVG have static imports. More to the point though, if you can resolve it at build time why not? When they say "This can be solved by using hashes of the file contents" this is a fundamental mistake and it's simply bad advice.
• saidajigumi 11y ago
  I find the Khan Academy analysis on compression to be missing any consideration of caching. They're seeing a 2.5% hit for compressing individual JS files vs. their existing JS bundles, or a ~16kb increase on a ~646kb baseline. That seems small enough that I'd also want to see modeling of the bandwidth savings from the finer-grained caching of individual files to get a more complete picture. As cited, only new[1] visitors to the site incur the hit stated, but this page is nominally the homepage for logged-in users. So it seems that recurring usage should be common here, but perhaps there's a non-intuitive usage pattern for their site? In any event, recurring visitors may have to redownload far less total bytes due to ongoing site changes given the improved cache locality of an individual JS file approach. OTOH, the Google App Engine webserver latency issue looks straightforward and is a great reminder to measure and analyze results for ongoing HTTP/2 deployments. [1] "new" as "cache miss on all JS assets"