4 ms·
Not exactly. It does do stuff concurrently, but not always in "parallel" since it may only have 1 core available or not get scheduled across multiple cores. I d
by anaphor 13y ago
Not exactly. It does do stuff concurrently, but not always in "parallel" since it may only have 1 core available or not get scheduled across multiple cores. I disagree with that particular wording of the systemd description because it perpetuates the concurrency == parallelism misunderstanding. Not that I don't like systemd, I've been using it for over a year and haven't had any issues, and its concurrent model does seem to improve boot times somewhat and there's no more figuring out how to order your daemons since it handles that for you.
- ambrop7 13y agoAnd there is no need to make it parallel. There is very little computation the init itself needs to do - most of the time it is waiting for things to happen, and the time it takes to react to events is negligible.