3 ms·
He spoke about the space savings of the binary itself (which must be debug things and statically linked code). There is no sharing of that , unless multiple pro
by jstimpfle 10y ago
He spoke about the space savings of the binary itself (which must be debug things and statically linked code). There is no sharing of that , unless multiple processes run that same binary.
- leeter 10y agoUnless the binary size exceeds VM page size this has no real value even in the unshared case. Because the OS is still going to have to map a full page for the executable to be loaded into. That said techniques to allow a binary to fit under page size do have value; as the unused extra page can be used for other things.
- jstimpfle 10y agoThat's totally true, and there is more overhead associated to processes. 8K executables are negligible. Some other languages produce executables in the dozens of megabytes.
- Symmetry 10y agoThe OS may map a full page for the binary but I'd expect that the time to load the binary from disk to memory would be saved. And once in memory the program would certainly take up fewer cache lines when executed.
- slededit 10y agoAt 4K the majority of the load from disk will be seek time (even on an SSD).