use a separate thread to write auth zones to disk #794
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.
Hi!
We ran into a problem on an installation with very large auth-zones.
For example, we have auth-zone with 30k records and up to 70 MB in size.
At the time of the auth-zone update, they are written to disk in the same thread in which the event loop processing user requests is running.
This behavior greatly hurts the event loop, which causes user request timeouts.
For example, here is the moment of writing an auth-zone with a size of 70 MB, this operation can last up to 4 seconds.
K - seconds
This means that this thread (when using SO_REUSEPORT) receives a user load, but cannot process it.
I made a simple patch that adds optional behavior for writing auth-zones in a separate thread.
Any suggestions are welcome!