github.com/lestrrat-go/jwx/v2@v2.0.21/.aspect/bazelrc/performance.bazelrc (about) 1 # Merkle tree calculations will be memoized to improve the remote cache hit checking speed. The 2 # memory foot print of the cache is controlled by `--experimental_remote_merkle_tree_cache_size`. 3 # Docs: https://bazel.build/reference/command-line-reference#flag--experimental_remote_merkle_tree_cache 4 build --experimental_remote_merkle_tree_cache 5 query --experimental_remote_merkle_tree_cache 6 7 # The number of Merkle trees to memoize to improve the remote cache hit checking speed. Even though 8 # the cache is automatically pruned according to Java's handling of soft references, out-of-memory 9 # errors can occur if set too high. If set to 0 the cache size is unlimited. Optimal value varies 10 # depending on project's size. 11 # Docs: https://bazel.build/reference/command-line-reference#flag--experimental_remote_merkle_tree_cache_size 12 build --experimental_remote_merkle_tree_cache_size=1000 13 query --experimental_remote_merkle_tree_cache_size=1000 14 15 # Speed up all builds by not checking if output files have been modified. Lets you make changes to 16 # the output tree without triggering a build for local debugging. For example, you can modify 17 # [rules_js](https://github.com/aspect-build/rules_js) 3rd party npm packages in the output tree 18 # when local debugging. 19 # Docs: https://github.com/bazelbuild/bazel/blob/1af61b21df99edc2fc66939cdf14449c2661f873/src/main/java/com/google/devtools/build/lib/pkgcache/PackageOptions.java#L185 20 build --noexperimental_check_output_files 21 fetch --noexperimental_check_output_files 22 query --noexperimental_check_output_files 23 24 # Don't apply `--noremote_upload_local_results` and `--noremote_accept_cached` to the disk cache. 25 # If you have both `--noremote_upload_local_results` and `--disk_cache`, then this fixes a bug where 26 # Bazel doesn't write to the local disk cache as it treats as a remote cache. 27 # Docs: https://bazel.build/reference/command-line-reference#flag--incompatible_remote_results_ignore_disk 28 build --incompatible_remote_results_ignore_disk 29 30 # Directories used by sandboxed non-worker execution may be reused to avoid unnecessary setup costs. 31 # Save time on Sandbox creation and deletion when many of the same kind of action run during the 32 # build. 33 # No longer experimental in Bazel 6: https://github.com/bazelbuild/bazel/commit/c1a95501a5611878e5cc43a3cc531f2b9e47835b 34 # Docs: https://bazel.build/reference/command-line-reference#flag--reuse_sandbox_directories 35 build --experimental_reuse_sandbox_directories 36 37 # Do not build runfiles symlink forests for external repositories under 38 # `.runfiles/wsname/external/repo` (in addition to `.runfiles/repo`). This reduces runfiles & 39 # sandbox creation times & prevents accidentally depending on this feature which may flip to off by 40 # default in the future. Note, some rules may fail under this flag, please file issues with the rule 41 # author. 42 # Docs: https://bazel.build/reference/command-line-reference#flag--legacy_external_runfiles 43 build --nolegacy_external_runfiles 44 run --nolegacy_external_runfiles 45 test --nolegacy_external_runfiles 46 47 # Some actions are always IO-intensive but require little compute. It's wasteful to put the output 48 # in the remote cache, it just saturates the network and fills the cache storage causing earlier 49 # evictions. It's also not worth sending them for remote execution. 50 # For actions like PackageTar it's usually faster to just re-run the work locally every time. 51 # You'll have to look at an execution log to figure out what other action mnemonics you care about. 52 # In some cases you may need to patch rulesets to add a mnemonic to actions that don't have one. 53 # https://bazel.build/reference/command-line-reference#flag--modify_execution_info 54 build --modify_execution_info=PackageTar=+no-remote