More data.
The truth is somewhere between absolute paths, relative paths, and sandbox size. Will probably investigate more when #13050 and #13160 are resolved.
This commit is contained in:
14
README.md
14
README.md
@@ -33,3 +33,17 @@ INFO: Elapsed time: 214.333s, Critical Path: 18.31s
|
||||
INFO: 385 processes: 193 internal, 192 linux-sandbox.
|
||||
INFO: Build completed successfully, 385 total actions
|
||||
```
|
||||
|
||||
Move sandbox to `/dev/shm` and reuse the sandboxes: 3 minutes and a bit.
|
||||
|
||||
```
|
||||
$ bazel clean; bazel shutdown; bazel build --sandbox_base=/dev/shm --experimental_reuse_sandbox_directories --platforms=@zig_sdk//libc_aware/platform:linux_amd64_gnu.2.28 ...
|
||||
INFO: Starting clean (this may take a while). Consider using --async if the clean takes more than several minutes.
|
||||
Starting local Bazel server and connecting to it...
|
||||
INFO: Analyzed 96 targets (41 packages loaded, 14394 targets configured).
|
||||
INFO: Found 96 targets...
|
||||
INFO: Elapsed time: 194.643s, Critical Path: 25.35s
|
||||
INFO: 385 processes: 193 internal, 192 linux-sandbox.
|
||||
INFO: Build completed successfully, 385 total actions
|
||||
motiejus@motiejus-20NYS8QG0B:/code/test-zigcc$
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user