You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 3, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1068,12 +1068,11 @@ Set this flag to indicate which build stage is the target build stage.
1068
1068
1069
1069
#### Flag `--use-new-run`
1070
1070
1071
-
Use the experimental RUN implementation for detecting changes without requiring
1072
-
Using this flag enables an experimental implementation of the Run command which does not rely on snapshotting at all.
1071
+
Using this flag enables an experimental implementation of the Run command which does not rely on snapshotting at all.
1073
1072
In this approach, in order to compute which files were changed, a marker file is created before executing the Run command.
1074
1073
Then the entire filesystem is walked (takes ~1-3 seconds for 700Kfiles) to find all files whose ModTime is greater than the marker file.
1075
1074
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
1076
-
off accuracy/correctness in some cases (potential for missed files in "snapshot") for improved performance by avoiding the full filesystem snapshots.
1075
+
off accuracy/correctness in some cases (potential for missed files in a "snapshot") for improved performance by avoiding the full filesystem snapshots.
0 commit comments