4 ms·
You would need find an application where the binary image size is a problem. In an age where 1TB SSDs are 300 USD this will be ... challenging. You are able to
by chx 8y ago
You would need find an application where the binary image size is a problem. In an age where 1TB SSDs are 300 USD this will be ... challenging. You are able to have about a thousand gigabyte sized images on that one SSD and I suspect you will hit CPU and I/O limits well before you have a thousand different binaries running for real.
Media storage would go on spinning rust disks anyways separate from the SSD(s).
- takeda 8y agoWe observed noticeable difference in deployment time and auto scaling based on container size.
- derefr 8y agoThe consideration isn’t binary size, but hot-loop cache coherency. Big binaries cause code-segment cache-line eviction.
- nolok 8y agoThen that's a typical case of optimizing on the wrong metric. Find a case where it's actually too slow, ok, but saying "A does X, and X can lead to Y, therefore A does Y" is wrong. If you say the size of the binary is an issue, then give the issue, not how it could (or not) be an issue.