-
Notifications
You must be signed in to change notification settings - Fork 183
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
Increase the resource limits on CPU and memory for fluentd deployment #43
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good testing you did! @samjsong This information is also useful for the baseline cc @ggarg2906sumo .
@@ -291,11 +291,11 @@ spec: | |||
imagePullPolicy: Always | |||
resources: | |||
limits: | |||
memory: 256Mi | |||
cpu: "100m" | |||
memory: 1000Mi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: make this 1Gi
. 1000Mi
is like the worst of both worlds... using base-2 nomenclature but giving it a base-10 value.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
haha, sounds good. thanks for the feedback Ryan
requests: | ||
memory: 256Mi | ||
cpu: "100m" | ||
memory: 700Mi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: stick to a base-2 value, 768Mi
Based on the metrics I collected on CPU and Memory usage, I feel these are reasonable numbers for request and limit. This is sufficient for collecting up to 5MB/sec = 432GB/day rates. For greater loads, we can either increase the number of Fluentd replicas, or increase the CPU limits. Memory usage seems to be relatively stable even with higher loads.
FYI @ggarg2906sumo @lei-sumo @maimaisie @yuting-liu @frankreno