3 ms·
My naive guess to what's going on is gzip here is set on tame settings, such that when it sees the same codeblock twice it shrinks it in a more space-efficient
by fsdsadlfkj 3y ago
My naive guess to what's going on is gzip here is set on tame settings, such that when it sees the same codeblock twice it shrinks it in a more space-efficient less cpu-efficient way. When it sees it just once, it doesn't.
However it happens, I think if you're being real, it would take A LOT of these micro-optimizations multiplied by A LOT of cache misses to add up to anything important.
What I got out of this is, unless you're looking at the specific bytes in the network tab every time you edit your code, just minify/gzip and forget about it.