jam HaikuDepot with nothing to do, best of many runs: hoard2 real 0m3.519s user 0m3.348s sys 0m0.159s openbsd real 0m3.481s user 0m3.327s sys 0m0.147s time printf "continue\nsave-report\nquit\nk\n" | Debugger -c Debugger -s 1000 hoard2 real 0m2.295s user 0m2.505s sys 0m0.128s openbsd real 0m2.896s user 0m2.809s sys 0m0.579s The performance difference in Debugger is due to OpenBSD malloc actually decommitting memory. If we disable decommit, then OpenBSD malloc is faster than hoard2 in this case also. In some particular cases this is a huge speedup. For example, the link of the "lto-dump" program in GCC seems to hit a pathological case in hoard2 and our glue code for it; with hoard2 it takes around 23 seconds, but with this allocator it takes only 2 seconds (!). Overall the performance difference is much more modest, though. Overall, system memory usage seems to be up about ~5% (318 MB -> 334 MB just after boot), and that seems to mostly be due to the allocator filling its initial caches faster when allocations occur, rather than lazily allocating. Change-Id: I071d8f76fbbfa11547bd6da6bf649d111414e780 Reviewed-on: https://review.haiku-os.org/c/haiku/+/8974 Reviewed-by: waddlesplash <waddlesplash@gmail.com> Haiku-Format: Haiku-format Bot <no-reply+haikuformatbot@haiku-os.org> Tested-by: Commit checker robot <no-reply+buildbot@haiku-os.org>
Haiku
Homepage | Mailing Lists | IRC Channels | Issue Tracker | API docs
Haiku is an open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.
Goals
- Sensible defaults with minimal configuration required.
- Clean, clear, concise code.
- Unified desktop environment.
Trying Haiku
Haiku provides pre-built nightly images and release images. Haiku is compatible with a large variety of hardware, but in case you don't want to "take the plunge" and install Haiku on bare metal, you can install it on a virtual machine (VM) instead. If you've never used a VM before, you can follow one of the "Emulating Haiku" guides.
Compiling Haiku
See ReadMe.Compiling
.
Contributing
Haiku is a meritocratic open source project with a large variety of tasks. Even if you can't write code, you can still help! Haiku needs designers, (technical) writers, translators, testers... Get involved and help out!
Contributing code
If you're submitting a patch to us, please make sure you're following the patch submitting guidelines.
If you're having trouble finding something in the source tree, you can use one of our web-based source code browsers:
- https://grok.nikisoft.one/opengrok/ (OpenGrok, provided by Niklas Poslovski)
- https://git.haiku-os.org/ (git, provided by Haiku, Inc.)
Contributing documentation
The main piece of documentation that still needs work are the API docs (found
in the tree at docs/user
). Just find an undocumented class, write
documentation for it, and submit a patch.
Contributing translations
See wiki:i18n.
Contributing software ports
See HaikuPorts.
Contributing to our infrastructure
See Infrastructure.