Memory matters

Hi all,

I have a question...

Why is it good to sucrifice some runtime memory to get a smaller static footprint (size of binaries) ?


  • [color=Blue]Small binaries are good for internet - the web pages are loaded faster, because a smaller component (which usually is downloaded by browser) will take a smaller time to get loaded.

    However, I do not see a connection between more memory and small size. You assume that a small size binary will take more memory to execute. That is determined by code in that binary, so it is not always true. Can you give an example of such sacrifice?[/color]
  • Memory footprint includes all sorts of active memory regions like code, static data sections (both initialized and uninitialized), heap, as well as all the stacks, plus memory required to hold any additional data structures, such as symbol tables, constant tables, debugging structures, open files, etc, that the program ever needs while executing and will be loaded at least once during the entire run.
  • It seems that it can improve your browsing speed. Of course, you can save a lot of time from that.
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!