Asynchronous Sending for RemoteSyslogAppender in log4net #253
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.
This PR addresses a major performance bottleneck in RemoteSyslogAppender, where synchronous .Wait() calls were blocking high-throughput applications.
Summary of Changes
Introduced a background task and queue (producer-consumer model) for async UDP sends
Removed thread-blocking .Wait() from Append() method
Ensured graceful shutdown with cancellation tokens
Documentation included at docs/AsynchronousSendingforRemoteSyslogAppenderinlog4net.pdf
Request
Please consider reviewing and including this change in a future release. We rely on log4net and would prefer not to maintain a separate fork.