Hacker News new | ask | show | jobs
by canucker2016 650 days ago
I don't see a Content-Encoding header on the response for the JS and HTML files, which suggests the 11.5MB JS and the HTML files aren't compressed.

Not much of a worry on the tiny HTML file, but the 11.5MB JS file should compress to a much smaller file on the wire.
2 comments
lneves12 648 days ago
ah I thought I was going crazy (I was sure this was working at some point). The compression just stopped working because of a cloudfront limitation eheh

`CloudFront compresses objects that are between 1,000 bytes and 10,000,000 bytes in size.` - since the file became bigger than 10mb, cloudfront stopped compressing it...

link
canucker2016 647 days ago
Well at least you know you weren't lazy/ignorant.

It's just that your tools make you look that way... and cost you more money in extra bandwidth as well. I hope that's the last of the surprises in that area.

link
lneves12 650 days ago
ah that's an embarrassing oversight! we reuse the same cdn configuration for multiple projects and for some reason the compression isn't properly configured for our portal-notebooks.singlestore.com entry point. It's funny that I reconfirmed that before publishing the blogpost, but mistakenly looked at the request headers and not the response headers (facepalm). We are fixing that now, thank you! This will be helpful for cases where you access the notebooks UI directly. For cases where you come from other page, it shouldn't make that much difference, since the iframe is already pre rendered.
link