4 ms·
Seems like this would result in quite a lot of increased server load. Previously servers would cache compressed versions of your static resources. Whereas now
by londons_explore 1y ago
Seems like this would result in quite a lot of increased server load.
Previously servers would cache compressed versions of your static resources.
Whereas now they either have to compress on-the-fly or have a massive cache of not only your most recent static JavaScript blob, but also all past blobs and versions compressed using different combinations of them as a dictionary.
This could easily 10x resources needed for serving static html/CSS/js.
- magicalist 1y agoThe past versions stored clientside are the dictionaries. Serverside, just keep the diffs against, say, the last five versions around if storage is an issue, or whatever gets you some high percentage of returning clients, then rebuild when pushing a new release.
- toast0 1y agoPresumably you'd generate a standalone compressed form (or forms) as usual, and also compressed forms using several dictionaries. Then the server is doing more work at request time, but it's not meaningfully more work --- just checking if the request path has a dictionary compressed form that matches the dictionary hash provided by the client.