5 ms·
It is not disk space you should be concerned with saving, but real memory usage. I wonder how much memory a statically liked Firefox uses under a heavy load.
by jmclnx 7y ago
It is not disk space you should be concerned with saving, but real memory usage. I wonder how much memory a statically liked Firefox uses under a heavy load. I checked with esr (what I use) and it is about a bit more that 1.3G excluding shared. So as firefox creates threads, I would think memory could get tight with a statically linked FF.
I fully agree with what OpenBSD has decided, I think the only thing worse that compiling Firefox is Gnome 3 :)
- ComputerGuru 7y agoStatically linked processes can’t share dependency pages with other, different processes. Multiple instances of the same process or multiple threads don’t have to incur that same penalty.
- ENOTTY 7y agoSeems to me that more aggressive memory deduplication at the kernel or hardware level should be able to mitigate memory explosion from using only statically linked binaries or letting “big” frequent updated projects manage their own dependencies.
- gdxhyrd 7y ago> So as firefox creates threads, I would think memory could get tight with a statically linked FF. Threads have nothing to do with that and don't increase memory usage due to dependencies.