382ddca7fc
The GCC "cc1plus" binary is over 40MB, so pre-faulting at most 10MB of it only helped so much. Now, we map 1 MB for every time the cache has been faulted "in full". This should warm up quite rapidly during compile jobs, and stabilize after that (with future faults mostly being CoW.) Only active (accessed+used) pages will get pre-mapped anyway, so if on a long-running system the page daemon debuffs all the pages in a cache, we would just iterate through all of them but not map any here. If that overhead proves to be a problem in the future, we can optimize for it then (probably by keeping track of how many pages are eligible for pre-mapping in this way.) This significantly reduces lock contention in compile jobs. Compiling libroot with a generated directory on ramfs and -j4, best of 3 runs: before: real 0m43.017s user 1m2.811s sys 0m24.900s after: real 0m29.367s user 1m0.321s sys 0m13.373s Change-Id: I441abf43803c8666cdc13c6d007bc04439698b0b Reviewed-on: https://review.haiku-os.org/c/haiku/+/8874 Reviewed-by: Michael Lotz <mmlr@mlotz.ch>
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.