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
2,140 types, 1,939 fields, and 8,997 methods found reachable
@@ -180,7 +180,7 @@ The memory limit and number of threads used by the build process.
180
180
More precisely, the memory limit of the Java heap, so actual memory consumption can be higher.
181
181
Please check the [peak RSS](#glossary-peak-rss) reported at the end of the build to understand how much memory was actually used.
182
182
The actual memory consumption can also be lower than the limit set, as the GC only commits memory that it needs.
183
-
By default, the build process uses the dedicated mode (which uses 85% of system memory) in containers or CI environments (when the `$CI` environment variable is set to `true`), but never more than 31GiB of memory.
183
+
By default, the build process uses the dedicated mode (which uses 85% of system memory) in containers or CI environments (when the `$CI` environment variable is set to `true`), but never more than 30GiB of memory.
184
184
Otherwise, it uses shared mode, which uses the available memory to avoid memory pressure on developer machines.
185
185
If less than 8GiB of memory are available, the build process falls back to the dedicated mode.
186
186
Therefore, consider freeing up memory if your machine is slow during a build, for example, by closing applications that you do not need.
0 commit comments