3 ms·
One of the other Haiku developers had this [1] response to an inquiry about why Haiku is so fast: > The system is not all that well optimized, uses a 15 year o
by waddlesplash 5y ago
One of the other Haiku developers had this [1] response to an inquiry about why Haiku is so fast:
> The system is not all that well optimized, uses a 15 year old compiler which does not uses any modern CPU features, and by default, the kernel is built in debug mode which makes it much slower than it could be.
> How do other operating systems still manage to feel slower? I have no idea.
(Those kernel debug options are no joke, they are a massive slowdown. The ones for the TCP stack alone take network throughput down to 1/5 of what it is without it; the ones for SMP, the virtual memory manager, lock facilities, etc. combined make the system visibly less snappy. We disable these on beta builds, but they are enabled on nightlies, and back in 2011 they were on by default.)
[1]: https://discuss.haiku-os.org/t/why-is-haiku-so-fast/6317 https://discuss.haiku-os.org/t/why-is-haiku-so-fast/6317
- nerdponx 5y agoIs the difference algorithmic/architectural?
- southerntofu 5y agoI'm not familiar with OS internals, but i believe having a system-wide consistent design (whole haiku is a monorepo) would enable you to simplify a lot of stuff. Also, many modern distros and desktop environments are bloated: you either have a choice between a full-featured, resource-hungry desktop (Gnome/KDE) or an efficient minimalist window manager (i3/sway). I believe the same applies to different parts/layers of the system. Haiku doesn't have the same feature set (yet) as full-featured modern desktops and doesn't have to deal with dozens of compatibility layers, so maybe that's also part of the reason it fares better.