Skip to content

Increase default resources for reaper#328

Open
maxnoe wants to merge 1 commit intorucio:masterfrom
maxnoe:resources-reaper
Open

Increase default resources for reaper#328
maxnoe wants to merge 1 commit intorucio:masterfrom
maxnoe:resources-reaper

Conversation

@maxnoe
Copy link
Copy Markdown
Contributor

@maxnoe maxnoe commented Mar 10, 2026

Fixes #327

@maxnoe maxnoe force-pushed the resources-reaper branch from 1651292 to cf731eb Compare March 10, 2026 10:40
@maxnoe maxnoe requested a review from bari12 March 10, 2026 10:40
Copy link
Copy Markdown
Contributor

@Soap2G Soap2G left a comment

Choose a reason for hiding this comment

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

Hi @maxnoe, thanks.
In my deployment I can e.g. see:

resources:
      limits:
        memory: "1600Mi"
        cpu: "800m"
      requests:
        memory: "125Mi"
        cpu: "30m"

And my pod is not OOM killed.
Were there any "systematic" tests as for what is the best config for the pod?

While the memory is kind on the same order of magnitude, the CPU requests are a factor 10 lower in my settings; so I'm wondering if I should update my settings, or how was the 700m decided?
Thanks!

@maxnoe
Copy link
Copy Markdown
Contributor Author

maxnoe commented Mar 10, 2026

Were there any "systematic" tests as for what is the best config for the pod?

No, I only observed our own monitoring and saw that the base usage (without any deletions happening) was already above the limit.

@maxnoe
Copy link
Copy Markdown
Contributor Author

maxnoe commented Mar 10, 2026

This is our monitoring for the reaper chugging along:

Screenshot_20260310_115153

Note that CPU limits are enforced differently than memory limits. For CPU, the workload is throttled, i.e. continues but slower. For memory, the pod is killed.

Copy link
Copy Markdown
Contributor

@Soap2G Soap2G left a comment

Choose a reason for hiding this comment

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

Looks fine to me, worst case scenario folks tune it to their needs.
Thanks!

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.

Default resources for reaper are too small

2 participants