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

Publish recommendations for memory limit, reservation, and swap #84

Open
jbisotti opened this issue Jun 6, 2019 · 2 comments
Open

Publish recommendations for memory limit, reservation, and swap #84

jbisotti opened this issue Jun 6, 2019 · 2 comments

Comments

@jbisotti
Copy link

jbisotti commented Jun 6, 2019

It would be helpful if there were some guidelines for the container's memory limit, reservation, & swap values.

@John1Q84
Copy link

I have been looking for the exactly same guidance.

I have a system which run on the AWS Fargate. And from Fargate, I would like to add sumo-collector container beside my app container as a 'side-car' pattern. So one Fargate task will have two containers. To do this, I need to set a memory limit/reservation for each container.

@maimaisie
Copy link
Collaborator

Hi, please take a look at the memory requirements for our installed collector: https://help.sumologic.com/01Start-Here/03About-Sumo-Logic/System-Requirements/Installed-Collector-Requirements

The dockerized collector should follow the same requirements as it is just essentially an installed collector wrapped inside a container.

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

No branches or pull requests

3 participants