Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: fix --use-new-run typo #2698

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -1068,12 +1068,11 @@ Set this flag to indicate which build stage is the target build stage.

#### Flag `--use-new-run`

Use the experimental RUN implementation for detecting changes without requiring
Using this flag enables an experimental implementation of the Run command which does not rely on snapshotting at all.
Using this flag enables an experimental implementation of the Run command which does not rely on snapshotting at all.
In this approach, in order to compute which files were changed, a marker file is created before executing the Run command.
Then the entire filesystem is walked (takes ~1-3 seconds for 700Kfiles) to find all files whose ModTime is greater than the marker file.
With this new run command implementation, the total build time is reduced seeing performance improvements in the range of ~75%. This new run mode trades
off accuracy/correctness in some cases (potential for missed files in "snapshot") for improved performance by avoiding the full filesystem snapshots.
off accuracy/correctness in some cases (potential for missed files in a "snapshot") for improved performance by avoiding the full filesystem snapshots.

#### Flag `--verbosity`

Expand Down