Use keepalive (requires a upstream block) + Open file cache#1221
Merged
Conversation
BentiGorlich
approved these changes
Nov 22, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
keepalivein Nginx, to actually keep the connection open. keepalive is not the max. amount of connections, but the amount of idle connections.open_file_cachegzip_comp_levelto 5 for a better balance between performance/CPU usage.For some reason Nginx think it's a good idea that this required an
upstreamblock, so actually in order to leverage keepalive functionality in Nginx, you will need to define an upstream section...Official keepalive documentation: http://nginx.org/en/docs/http/ngx_http_upstream_module.html#keepalive
And open file cache documentation here: http://nginx.org/en/docs/http/ngx_http_core_module.html#open_file_cache