feat: support configuring the buffer size of the access log #10225
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.
Description
access log's buffer size can be configed.
Access log buffering can significantly reduce disk I/O and improve server performance. Enabling access log buffering is relatively simple in NGINX. To do this, use the following directive in your NGINX configuration:
access_log /var/log/nginx/access.log main buffer=32k;
This directive tells NGINX to store the access log entries in a buffer of size 32k before writing them to the log file. Increasing the buffer size can minimize the number of write operations to the disk, resulting in improved performance.
Fixes #10219
Checklist