3 ms·
>Memory consumption is bloated and the CPU caches thrash. Launching a subprocess is expensive Statically and dynamically loaded binaries are resident in the ke
by valarauca1 9y ago
>Memory consumption is bloated and the CPU caches thrash. Launching a subprocess is expensive
Statically and dynamically loaded binaries are resident in the kernel's page cache. Which while each process will have different locations within its process address space for each process (b/c ALSR), they _should_ be de-duplicated in RAM, ultimately all these seperate in process images will be pointing at the same physical RAM page(s).
So from a hardware cache standpoint you're mostly okay.
- Animats 9y agoThat's just the interpreter's executable. All the stuff that's generated from the Python code you load, and any data it generates, is unique to the process.
- dom0 9y agoWith Python that's a lot of stuff; I suggest running strace python some_small_script.py to see just how much data Python loads on every single startup.