Hacker News Reader

The first thing a 5 MB upx-compressed binary does when executed is uncompress itself to 15~30 MB of memory, right? So what does the on-disk binary size have to do with my L3 cache?

Yup, upx is just a loading stub that decompresses the whole thing then gets out the way.

If anything it'll use more memory from the remains of the decompression stub and not being able to be clever about only reading from the backing file needed memory pages.

Uncompressed is less than 10MB.

So instead of 10MB you're paying 15MB? Seems like UPX is an unnecessary dependency.

Does that improve the usage of it? Have you experimented with larger sizes?

Thank you for Sidekiq, Mike :-D