3 ms·
Thank you! That sounds pretty different in implementation from zygote processes though: Zygote processes do go through the initialization once, but then clone
by lxgr 2y ago
Thank you! That sounds pretty different in implementation from zygote processes though:
Zygote processes do go through the initialization once, but then clone that pre-initialized state via forking. That makes launches faster, but importantly also reduces memory usage by sharing effectively read-only dirty memory across all processes (e.g. everything read into memory by each process via read() instead of memory mapping).
dyld closures seem to be caching process-specific linking precalculations, and prewarming just opportunistically (pre-)launches an app in case it's needed later. Same effect (faster launch time), but probably no memory savings, and a very different implementation.
- saagarjha 2y agoYes to be clear when I said "iOS does this" I meant "kinda similar to the whole freeze and restore thing" (which is the general topic here) not "the exact thing Android is doing"