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

cli: Make the CLI cgroups-aware #8234

Closed
wants to merge 1 commit into from
Closed

cli: Make the CLI cgroups-aware #8234

wants to merge 1 commit into from

Conversation

fmeum
Copy link
Contributor

@fmeum fmeum commented Jan 23, 2025

Honoring cgroups limits on CPUs is useful when running bb explain in a workflow, such as in the "Compare" Bazel button.

Honoring cgroups limits on CPUs is useful when running `bb explain` in a workflow, such as in the "Compare" Bazel button.
@fmeum fmeum requested a review from bduffany January 23, 2025 15:00
Copy link
Member

@bduffany bduffany left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Honoring cgroups limits on CPUs is useful when running bb explain in a workflow, such as in the "Compare" Bazel button.

When the CLI is run within workflows, there are no cgroup hard limits applied. The CPU limit is effectively determined by the number of vCPUs that we allocate to the firecracker VM.

I think this change doesn't hurt though so I'd be cool with merging.

@fmeum
Copy link
Contributor Author

fmeum commented Jan 23, 2025

Interesting find along the way: https://news.ycombinator.com/item?id=42248550

@fmeum
Copy link
Contributor Author

fmeum commented Jan 23, 2025

automaxprocs doesn't support cgroups v2. I'll drop this for now, thanks for the explanation.

@fmeum fmeum closed this Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants