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

As an admin I have configuration recommendations for low-bandwidth scenarios #1059

Open
ipanova opened this issue Sep 14, 2022 · 0 comments
Open
Labels
Docs Improvements or additions to documentation Feature

Comments

@ipanova
Copy link
Member

ipanova commented Sep 14, 2022

Describe the solution you'd like
As an admin I have docs which help me understand what values/settings to tune to overcome bottlenecks during container image push

Depending on the user base there might be quite a lot of concurrent image push also push of large images.
Admins need to know how and whether it is possible to improve the situation whenever 503/504 errors are surfaces to the end user.

There are server/system config that can be tuned like nginx values, socket max connections, number of file descriptions, worker timeouts, etc.

  • client_max_body_size, the default is 1m, it can/should be adjusted for a more performant podman push
  • gunicorn timeout can/should be increased to mitigate 504 error during a lot of simultaneous podman push which would lead to i/o saturation.

Network bandwith, disk iops, memory and cpu values need to be taken into account too.

Additional context
https://issues.redhat.com/browse/AAP-1729

@ipanova ipanova added the Docs Improvements or additions to documentation label Mar 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Docs Improvements or additions to documentation Feature
Projects
Status: Not Started
Development

No branches or pull requests

1 participant