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

Relax max_requests #295

Merged
merged 1 commit into from
Aug 8, 2023
Merged

Relax max_requests #295

merged 1 commit into from
Aug 8, 2023

Conversation

dralley
Copy link
Contributor

@dralley dralley commented Jul 20, 2023

The root cause of the memory leak has been established and resolved, so these aggressive values are no longer necessary

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,
Copy link
Contributor Author

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.

@ekohl
Copy link
Member

ekohl commented Jul 20, 2023

The root cause of the memory leak has been established and resolved, so these aggressive values are no longer necessary

Out of interest: can you share a link?

@dralley
Copy link
Contributor Author

dralley commented Jul 20, 2023

@ekohl pulp/pulpcore#4090

@ekohl
Copy link
Member

ekohl commented Jul 20, 2023

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.

@dralley
Copy link
Contributor Author

dralley commented Jul 20, 2023

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.

@dralley
Copy link
Contributor Author

dralley commented Jul 20, 2023

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
@dralley
Copy link
Contributor Author

dralley commented Jul 20, 2023

@ekohl Pushed

@ekohl
Copy link
Member

ekohl commented Jul 27, 2023

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.

@ekohl ekohl added the Enhancement New feature or request label Aug 8, 2023
@ekohl ekohl merged commit 54dffde into theforeman:master Aug 8, 2023
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants