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

Percentage settings for memory ballast #1828

Closed
pavolloffay opened this issue Sep 22, 2020 · 6 comments
Closed

Percentage settings for memory ballast #1828

pavolloffay opened this issue Sep 22, 2020 · 6 comments

Comments

@pavolloffay
Copy link
Member

Is your feature request related to a problem? Please describe.

I want to configure ballast size relative to the total system memory. This is helpful in a dynamic environments like docker/k8s.

Describe the solution you'd like

Add --mem-ballast-size-percentage flag and ballast_size_percentage to memory limiter. This will leave us with _mib settings and percentage settings, the mib having higher precedence.

I don't like that the ballast is being configured in two places - flag and memory limiter. Could we just support the blast in the memory limiter?

Describe alternatives you've considered
We have agreed to implement percentage for the ballast.

Additional context

Related to #1078
Created from #1622 (comment)

@pavolloffay
Copy link
Member Author

@bogdandrutu @tigrannajaryan @pjanotti could you please comment on this one? Whether we want to remove the ballast flags nad move the allocation to the memory limiter. Or the memory limiter could read flag values.

@pjanotti
Copy link
Contributor

Could we just support the blast in the memory limiter?

My intention was to have use the capability of retrieving maximum memory to have the ballast enabled by default due its cpu savings, however, it needs to be configurable. The memory limiter is an orthogonal concern that needs access to the ballast setting to operate correctly and for which I had seem practical cases it which it was applied selectively to different pipelines under same configuration. I don't think it makes sense to move the ballast to the memory limiter.

It seems reasonable to expose an application level setting like the ballast to components in general. We discussed this in the past. Would you like to put a proposal on how to do that?

@tigrannajaryan
Copy link
Member

Yes, ideally expose an interface for components to read global application settings. The memory limiter can find out the ballast size and configure itself accordingly.

@mxiamxia
Copy link
Member

#2516

@mxiamxia
Copy link
Member

this issue can be closed! the request has been addressed in #2516

@pavolloffay
Copy link
Member Author

I think this is done, closing

hughesjj pushed a commit to hughesjj/opentelemetry-collector that referenced this issue Apr 27, 2023
…y#1828)

Bumps [boto3](https://github.com/boto/boto3) from 1.24.42 to 1.24.44.
- [Release notes](https://github.com/boto/boto3/releases)
- [Changelog](https://github.com/boto/boto3/blob/develop/CHANGELOG.rst)
- [Commits](boto/boto3@1.24.42...1.24.44)

---
updated-dependencies:
- dependency-name: boto3
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Troels51 pushed a commit to Troels51/opentelemetry-collector that referenced this issue Jul 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants