6d336fda4a
We now record how long it takes to write a block (on average), and then utilize this information to reduce the timeout write thread's timeout (to 2 * block_count * average_block_time, so we don't completely congest the drive.) Remove the "TODO" about the I/O scheduler; this new logic will be just fine even under an I/O scheduler. Note that this change goes both ways: while faster writes mean more writes and quicker, slower writes will increase the timeout before we do another one also. This then also guards against queueing another write while one is already in progress, which was not handled before. Tested in KVM. Even on a SATA-backed spinning HDD, this reduces the timeout to around *200ms* on average (!!), so a 10x improvement. On a ramdisk, it reduces the timeout to *10-30ms* (!!!) on average, so a 100-200x improvement, so this change will benefit everyone but SSDs especially. Since BFS inode and journal writes always go through the block_cache, this very dramatically improves inode-related write performance. The "stop and start" stutters when emptying or moving items to Trash seem totally gone, among a lot of other things. Change-Id: I41f46a6432ce1f50f896a853abdfe22dde0ba327 |
||
|---|---|---|
| 3rdparty | ||
| build | ||
| data | ||
| docs | ||
| headers | ||
| src | ||
| .editorconfig | ||
| .gitignore | ||
| .gitreview | ||
| configure | ||
| Jamfile | ||
| Jamrules | ||
| License.md | ||
| ReadMe.Compiling.md | ||
| ReadMe.md | ||
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 OpenGrok servers:
- http://xref.plausible.coop/ (provided by Landon Fuller)
- http://code.metager.de/source/xref/haiku (provided by MetaGer)
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.