4 ms·
I develop and maintain a plurality of custom linux distros for embedded hardware using Yocto. I used to be the InitV guy, the first half of my distros use it a
by dcahill-ieee 3y ago
I develop and maintain a plurality of custom linux distros for embedded hardware using Yocto. I used to be the InitV guy, the first half of my distros use it and it's horrible. Every change breaks something. Services start and don't stop or vice versa. I recently switched to using Systemd and life is so much better. You can actually reason about systemd's operation and load order. The systems I build linux for have 128MB of ram up to 1GB of ram, are mostly 32 bit and use SD-Card like storage. In other words not exactly super performant and systemd boots in the same time as InitV. At worst it's 2-3 seconds slower. If I can't tell the difference on a $20 microprocessor I guarantee you can't either on the current state of the art CPU's. For reference my latest systemd based distro is 32 bits, runs at 400MHz and possesses a proud 200bogoMips of grunt.
- davrosthedalek 3y agoI don't think people complain about systemd being slow. It's supposed to be faster than initV because of parallel/delayed startup. But initV is the wrong comparison point anyway. Runit, upstart, openRC are all much better than initV. I certainly had less problems with openRC on my gentoo box than with systemD on my ubuntu box -- mainly because of all the add-ons (ntp, dns etc.) beyond init itself.