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

Revision to httpOption maxKeepAliveRequest default value #17040

Closed
mrsaldana opened this issue May 4, 2021 · 0 comments · Fixed by #17073
Closed

Revision to httpOption maxKeepAliveRequest default value #17040

mrsaldana opened this issue May 4, 2021 · 0 comments · Fixed by #17073
Assignees
Labels
in:Transport release bug This bug is present in a released version of Open Liberty release:21006 team:Sirius

Comments

@mrsaldana
Copy link
Member

By default, the Liberty HTTP channel configuration closes an incoming HTTP keep alive connection after 100 requests (maxKeepAliveRequests). The WAS Liberty performance documentation recommends disabling this without qualification and recommends using unlimited requests per persistent connection (). Hare & Blythe (2011) noted a 100% throughput improvement with this option on WAS traditional when using TLS (and that was with older and cheaper ciphers). Note that there is still the persistent timeout of 30 seconds (persistTimeout) which closes an idle keepalive socket after 30 seconds.

After revising this performance gain and discussing it internally, it was decided to change the default of the maxKeepAliveRequests option to -1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in:Transport release bug This bug is present in a released version of Open Liberty release:21006 team:Sirius
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants