4 ms·
This is likely to consume more memory, because of copy on write pages (or lack of thereof). Implementing the prefork model by spawning unrelated processes (by
by fooyc 13y ago
This is likely to consume more memory, because of copy on write pages (or lack of thereof).
Implementing the prefork model by spawning unrelated processes (by opposition to forking from a common parent process) is likely to consume more memory: each process is unrelated, and do not share copy on write memory pages with other processes.
- nullc 13y agoShared library code already gets shared, so this may not be as bad as you think.
- justincormack 13y agoYou could use SO_REUSEPORT with threads too. Linux threads are processes after all, with tweaked clone() options.