fb0b77979a
While profiling with iperf for #18203 I noticed that the default MTU for the loopback interface is 16KiB. Other operating systems set this quite a bit higher. Linux sets it to 64KiB by default. Random Google searches seem to suggest that Microsoft sets it even higher than this although I don't have a Windows computer to verify this at the moment. Changing the default to 64KiB in this patch makes a pretty big difference in a kvm VM with a single CPU. The max throughput goes from about 2Mbps/s to around 12Mbps/s, around a 6x increase. With the same VM but 8 CPUs, the throughput goes from 1.58Gbps to 1.99Gbps, about a 26% increase in throughput. It seems the throughput is a little more stable too and doesn't drop periodically. I suspect that this is just because there is less CPU saturation in the loop consumer thread. With window size maxed out to around 1GiB as described in #15886 there is still about a 10% increase in throughput with this change. There are still some weird performance issues to diagnose but this seems like a better default. Change-Id: I8c5d088298a4a7b3e8b1aa1a2f4f85b0cc9c62c2 Reviewed-on: https://review.haiku-os.org/c/haiku/+/6000 Reviewed-by: waddlesplash <waddlesplash@gmail.com>
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://xref.landonf.org/ (OpenGrok, provided by Landon Fuller)
- 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.