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.

Sign up for GitHub

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

Jump to bottom

docs: Add best practice for reducing memory usage #2545

Merged
merged 1 commit into from
Jan 27, 2023
Merged

docs: Add best practice for reducing memory usage #2545

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion docs/best-practices.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,4 +51,13 @@ spec:
```

The above technique has the a benefit in that it would not incur additional cost of allocating
additional load balancers.
additional load balancers.

## Reducing operator memory usage

On clusters with thousands of rollouts memory usage for the argo-rollouts
operator can be reduced significantly by changing RevisionHistoryLimit from the
default of 10 to a lower number. One user of Argo Rollouts saw a 27% reduction
in memory usage for a cluster with 1290 rollouts by changing
RevisionHistoryLimit from 10 to 0.