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

[backport -> release/3.2.x] perf(proxy): use more reasonable keepalive default value for Nginx tuning #12532

Closed
wants to merge 2 commits into from

Conversation

chobits
Copy link
Contributor

@chobits chobits commented Feb 5, 2024

backport #12223
also backport this PR: https://github.com/Kong/kong-ee/pull/6507

Summary

Bumped default values of nginx_http_keepalive_requests and upstream_keepalive_max_requests to 10000.

Checklist

  • The Pull Request has tests
  • A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
  • There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Issue reference

Fix KAG-3360

dndx and others added 2 commits February 5, 2024 11:23
…11515)

Bumped the default value of `upstream_keepalive_pool_size` to `512` and `upstream_keepalive_max_requests` to `1000`.

FTI-4868
…ing (#12223)

Bumped default values of `nginx_http_keepalive_requests` and
`upstream_keepalive_max_requests` to `10000`.

KAG-3360

---------

Co-authored-by: Datong Sun <[email protected]>
(cherry picked from commit f7e6eee)
@chobits chobits changed the title Backport 12223 to release/3.2.x [backport -> release/3.2.x] perf(proxy): use more reasonable keepalive default value for Nginx tuning Feb 5, 2024
@chobits
Copy link
Contributor Author

chobits commented Feb 5, 2024

Because 3.2.x has been deprecated, so we do not need to backport it to 3.2.x now.

Kong Gateway 3.2 will enter its end-of-life (EOL) phase in Feb 2024

@chobits chobits closed this Feb 5, 2024
@chronolaw chronolaw deleted the backport-12223-to-release/3.2.x branch February 5, 2024 07:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants