Re:Go: Planning the 1.5 release
by Animats on Tuesday December 02, 2014 @01:09PM
(#8688684)
Are shared libraries a memory win in production environments? For shared libraries to be a win, you have to be running different executables on the same machine (or VM) which share libraries of significant size relative to the memory use of the program itself.
You also have to be using a big fraction of each shared library. With static linking, if you need "cos", you get that loaded; with a shared library, you bring in the entire math library.
Modern production environments often involve only one program per VM, or multiple instances of the same program. In such cases, shared libraries are a lose.
Modern production environments often involve only one program per VM, or multiple instances of the same program. In such cases, shared libraries are a lose.