| commit | a5eaeb8670b0b56f884fbda8ddb92ea0bf78fb5d | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@nexantic.com> | Thu Jul 16 15:06:50 2020 +0200 |
| committer | Lorenz Brun <lorenz@nexantic.com> | Thu Jul 16 15:06:50 2020 +0200 |
| tree | 9cf2ea8bcfb5ee1170f4055979a69a0cd4266ab9 | |
| parent | f042e6f95bb7dc771bf79f309dbdf0b34da933da [diff] |
Increase zeroing performance for data partition It's possible to increase queue depth for O_DIRECT in simple cases like ours by just submitting bigger buffers. As long as they are an exact multiple of the block size this is fine and the kernel doesn't complain. This also enables O_SYNC to prevent any buffering on the guest. This should help to push out data quicker and prevent buffer bloat. The host has its own cache anyways. Test Plan: No change in functionality, I observe more predictable performance (previously I sometimes had stalls where the initialization would take > 60s). X-Origin-Diff: phab/D599 GitOrigin-RevId: 19554fd9e6d709bde738d01a0d2de190c441640e
This is the monorepo storing all of nexantic's internal projects and libraries.
We assume a Fedora host system provisioned using rW, and IntelliJ as the IDE.
For better reproducibility, all builds are executed in containers.
Spinning up: scripts/create_container.sh
Spinning down: scripts/destroy_container.sh
Running commands: scripts/run_in_container.sh <...>
Using bazel using a wrapper script: scripts/bin/bazel <...> (add to your local $PATH for convenience)
Launch the node:
bazel run //:launch
Run a kubectl command:
bazel run //core/cmd/dbg -- kubectl describe
This repository is compatible with the IntelliJ Bazel plugin. All commands run inside the container, and necessary paths are mapped into the container.
We check the entire .ijwb project directory into the repository, which requires everyone to use the latest version of both IntelliJ and the Bazel plugin, but eliminates manual setup steps.
The following steps are necessary:
Install Google's official Bazel plugin in IntelliJ.
Add the absolute path to your ~/.cache/bazel-nxt folder to your idea64.vmoptions (Help → Edit Custom VM Options) and restart IntelliJ:
-Dbazel.bep.path=/home/leopold/.cache/bazel-nxt
Set "Bazel Binary Location" in Other Settings → Bazel Settings to the absolute path of scripts/bin/bazel. This is a wrapper that will execute Bazel inside the container.
Open the .ijwb folder as IntelliJ project.
Disable Vgo support for the project.
Run a non-incremental sync in IntelliJ
The plugin will automatically resolve paths for generated files.
If you do not use IntelliJ, you need to use the scripts/bazel_copy_generated_for_ide.sh script to copy files locally.