Set --defer_param_files to true.

This will cause bazel to write the parameter file during action execution instead of as a separate action. This is faster and requires less memory than using a separate action.

When using remote execution, pass --materialize_param_files if you wish to inspect the file locally (for debugging purposes).

RELNOTES: Set --defer_param_files to default to true.
PiperOrigin-RevId: 207300073

1 files changed, 2 insertions, 2 deletions

diff --git a/src/main/java/com/google/devtools/build/lib/analysis/config/BuildConfiguration.java b/src/main/java/com/google/devtools/build/lib/analysis/config/BuildConfiguration.java
index 582aa253d0..9a9b8de17b 100644
--- a/src/main/java/com/google/devtools/build/lib/analysis/config/BuildConfiguration.java
+++ b/src/main/java/com/google/devtools/build/lib/analysis/config/BuildConfiguration.java
@@ -382,7 +382,7 @@ public class BuildConfiguration implements BuildConfigurationApi {
 
     @Option(
         name = "defer_param_files",
-        defaultValue = "false",
+        defaultValue = "true",
         documentationCategory = OptionDocumentationCategory.UNDOCUMENTED,
         effectTags = {
           OptionEffectTag.LOADING_AND_ANALYSIS,
@@ -390,7 +390,7 @@ public class BuildConfiguration implements BuildConfigurationApi {
           OptionEffectTag.ACTION_COMMAND_LINES
         },
         help =
-            "Whether to use deferred param files. WHen set, param files will not be "
+            "Whether to use deferred param files. When set, param files will not be "
                 + "added to the action graph. Instead, they will be added as virtual action inputs "
                 + "and written at the same time as the action executes.")
     public boolean deferParamFiles;