-
Notifications
You must be signed in to change notification settings - Fork 28
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
Relax max_requests #295
Relax max_requests #295
Conversation
Integer[0] $api_service_worker_max_requests = 50, | ||
Integer[0] $api_service_worker_max_requests_jitter = 30, | ||
Integer[0] $api_service_worker_max_requests = 800, | ||
Integer[0] $api_service_worker_max_requests_jitter = 100, |
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.
These seem reasonable to me, but they're just spitballs. Probably 4,000 and 500 would be fine too.
Out of interest: can you share a link? |
Thanks. How one line can make such a big difference. That looks very recent so I'd like to see it propagate through packaging. It also needs updated tests to reflect the new numbers. |
I believe the tests are testing changing those values rather than the current values, so they don't need to be changed. Unless you mean something else. |
Oh, there's tests that weren't added in the previous PR that I missed. |
The root cause of the memory leak has been established and resolved, so these aggressive values are no longer necessary
@ekohl Pushed |
https://ci.theforeman.org/job/pulpcore-3.22-rpm-pipeline/ is still blocked (there was some issue in CentOS CI) and I'd like to wait for that to pass. |
The root cause of the memory leak has been established and resolved, so these aggressive values are no longer necessary