Size and Memory Optimizations
Discussions debate the value of small optimizations for reducing memory usage, binary size, disk space, and bandwidth, weighing marginal savings against added complexity and overhead.
Activity Over Time
Top Contributors
Keywords
Sample Comments
You're talking about saving _at most_ 200MBish. That's a lot of work to maintain for little gain...
At least they're saving on memory, to be fair.
That's a lot of extra character overhead for not very much gain.
Sure the relative lost efficiency from that extra 20kb may be
The savings is marginal, but if you are able to set it up once and forget it, why not take advantage of a few % reduction in page size?
The cost per byte would go down but the number of bytes would go up.
The savings is marginal, but why not configure your solution to save extra bytes then forget it is even there?
Were they trying to save memory?
Not much compute and memory to be saved. You can save on storage, but who cares about that?
Sounds like a lot of space wasted?