Skip to content

docs: Update documentation for deprecated local resource flags #96

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.

Sign up for GitHub

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

Open
promptless wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: Update documentation for deprecated local resource flags #96

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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 7.6.1/advanced/performance/build-performance-breakdown.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,9 +144,8 @@ system load average during the invocation.

A high load during a Bazel invocation can be an indication that Bazel schedules
too many local actions in parallel for your machine. You might want to look into
adjusting
[`--local_cpu_resources`](/reference/command-line-reference#flag--local_cpu_resources)
and [`--local_ram_resources`](/reference/command-line-reference#flag--local_ram_resources),
adjusting [`--local_resources`](/reference/command-line-reference#flag--local_resources)
(e.g., `--local_resources=cpu=HOST_CPUS*.5` or `--local_resources=memory=HOST_RAM*.5`),
especially in container environments (at least until
[#16512](https://github.com/bazelbuild/bazel/pull/16512) is merged).

Expand Down
5 changes: 2 additions & 3 deletions 8.0.1/advanced/performance/build-performance-breakdown.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,9 +144,8 @@ system load average during the invocation.

A high load during a Bazel invocation can be an indication that Bazel schedules
too many local actions in parallel for your machine. You might want to look into
adjusting
[`--local_cpu_resources`](/reference/command-line-reference#flag--local_cpu_resources)
and [`--local_ram_resources`](/reference/command-line-reference#flag--local_ram_resources),
adjusting [`--local_resources`](/reference/command-line-reference#flag--local_resources)
(e.g., `--local_resources=cpu=HOST_CPUS*.5` or `--local_resources=memory=HOST_RAM*.5`),
especially in container environments (at least until
[#16512](https://github.com/bazelbuild/bazel/pull/16512) is merged).

Expand Down
5 changes: 2 additions & 3 deletions 8.1.1/advanced/performance/build-performance-breakdown.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,9 +144,8 @@ system load average during the invocation.

A high load during a Bazel invocation can be an indication that Bazel schedules
too many local actions in parallel for your machine. You might want to look into
adjusting
[`--local_cpu_resources`](/reference/command-line-reference#flag--local_cpu_resources)
and [`--local_ram_resources`](/reference/command-line-reference#flag--local_ram_resources),
adjusting [`--local_resources`](/reference/command-line-reference#flag--local_resources)
(e.g., `--local_resources=cpu=HOST_CPUS*.5` or `--local_resources=memory=HOST_RAM*.5`),
especially in container environments (at least until
[#16512](https://github.com/bazelbuild/bazel/pull/16512) is merged).

Expand Down
5 changes: 2 additions & 3 deletions 8.2.1/advanced/performance/build-performance-breakdown.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,9 +144,8 @@ system load average during the invocation.

A high load during a Bazel invocation can be an indication that Bazel schedules
too many local actions in parallel for your machine. You might want to look into
adjusting
[`--local_cpu_resources`](/reference/command-line-reference#flag--local_cpu_resources)
and [`--local_ram_resources`](/reference/command-line-reference#flag--local_ram_resources),
adjusting [`--local_resources`](/reference/command-line-reference#flag--local_resources)
(e.g., `--local_resources=cpu=HOST_CPUS*.5` or `--local_resources=memory=HOST_RAM*.5`),
especially in container environments (at least until
[#16512](https://github.com/bazelbuild/bazel/pull/16512) is merged).

Expand Down
5 changes: 2 additions & 3 deletions 8.3.1/advanced/performance/build-performance-breakdown.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,9 +144,8 @@ system load average during the invocation.

A high load during a Bazel invocation can be an indication that Bazel schedules
too many local actions in parallel for your machine. You might want to look into
adjusting
[`--local_cpu_resources`](/reference/command-line-reference#flag--local_cpu_resources)
and [`--local_ram_resources`](/reference/command-line-reference#flag--local_ram_resources),
adjusting [`--local_resources`](/reference/command-line-reference#flag--local_resources)
(e.g., `--local_resources=cpu=HOST_CPUS*.5` or `--local_resources=memory=HOST_RAM*.5`),
especially in container environments (at least until
[#16512](https://github.com/bazelbuild/bazel/pull/16512) is merged).

Expand Down
5 changes: 2 additions & 3 deletions 8.4.2/advanced/performance/build-performance-breakdown.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,9 +144,8 @@ system load average during the invocation.

A high load during a Bazel invocation can be an indication that Bazel schedules
too many local actions in parallel for your machine. You might want to look into
adjusting
[`--local_cpu_resources`](/reference/command-line-reference#flag--local_cpu_resources)
and [`--local_ram_resources`](/reference/command-line-reference#flag--local_ram_resources),
adjusting [`--local_resources`](/reference/command-line-reference#flag--local_resources)
(e.g., `--local_resources=cpu=HOST_CPUS*.5` or `--local_resources=memory=HOST_RAM*.5`),
especially in container environments (at least until
[#16512](https://github.com/bazelbuild/bazel/pull/16512) is merged).

Expand Down
5 changes: 2 additions & 3 deletions advanced/performance/build-performance-breakdown.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,9 +144,8 @@ system load average during the invocation.

A high load during a Bazel invocation can be an indication that Bazel schedules
too many local actions in parallel for your machine. You might want to look into
adjusting
[`--local_cpu_resources`](/reference/command-line-reference#flag--local_cpu_resources)
and [`--local_ram_resources`](/reference/command-line-reference#flag--local_ram_resources),
adjusting [`--local_resources`](/reference/command-line-reference#flag--local_resources)
(e.g., `--local_resources=cpu=HOST_CPUS*.5` or `--local_resources=memory=HOST_RAM*.5`),
especially in container environments (at least until
[#16512](https://github.com/bazelbuild/bazel/pull/16512) is merged).

Expand Down
8 changes: 8 additions & 0 deletions reference/command-line-reference.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4464,6 +4464,10 @@ Tags:

`--local_cpu_resources=<an integer, or "HOST_CPUS", optionally followed by [-|*]<float>.>` default: "HOST\_CPUS"

<Warning>
**Deprecated:** This flag is deprecated. Use [`--local_resources`](#flag--local_resources) instead with `cpu=<value>` syntax (e.g., `--local_resources=cpu=HOST_CPUS*.5`).
</Warning>

Explicitly set the total number of local CPU cores available to Bazel to spend on build actions executed locally. Takes an integer, or "HOST\_CPUS", optionally followed by \[-\| _\]<float> (eg. HOST\_CPUS_.5 to use half the available CPU cores). By default, ("HOST\_CPUS"), Bazel will query system configuration to estimate the number of CPU cores available.

Tags:
Expand All @@ -4478,6 +4482,10 @@ Tags:

`--local_ram_resources=<an integer number of MBs, or "HOST_RAM", optionally followed by [-|*]<float>.>` default: "HOST\_RAM\*.67"

<Warning>
**Deprecated:** This flag is deprecated. Use [`--local_resources`](#flag--local_resources) instead with `memory=<value>` syntax (e.g., `--local_resources=memory=HOST_RAM*.5`).
</Warning>

Explicitly set the total amount of local host RAM (in MB) available to Bazel to spend on build actions executed locally. Takes an integer, or "HOST\_RAM", optionally followed by \[-\| _\]<float> (eg. HOST\_RAM_.5 to use half the available RAM). By default, ("HOST\_RAM\*.67"), Bazel will query system configuration to estimate the amount of RAM available and will use 67% of it.

Tags:
Expand Down
Loading