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

Investigate disabling memory over commit and/or the OOM killer #38

Open
shuhaowu opened this issue Apr 27, 2022 · 2 comments
Open

Investigate disabling memory over commit and/or the OOM killer #38

shuhaowu opened this issue Apr 27, 2022 · 2 comments

Comments

@shuhaowu
Copy link
Member

No description provided.

@shuhaowu
Copy link
Member Author

shuhaowu commented Sep 1, 2022

I think disabling these by default may have some negative side effects for non-RT applications. The benefit for RT application is rather minor, if the RT application is properly coded. Unless there's a good reason to enable this, I'm actually thinking of not enabling this for now. That said, we may consider this again in the future?

@carlossvg
Copy link
Collaborator

I think disabling these by default may have some negative side effects for non-RT applications. The benefit for RT application is rather minor, if the RT application is properly coded. Unless there's a good reason to enable this, I'm actually thinking of not enabling this for now. That said, we may consider this again in the future?

@shuhaowu I agree. This was more related to running benchmarks under heavy memory stress but you can always enable it specifically for the tests.

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

2 participants