Revamp the Asynchronous logging page
#2534
Assignees
Labels
documentation
Pull requests or issues that affect documentation
Comments
ppkarwasz
added a commit
that referenced
this issue
May 14, 2024
We refresh the asynchronous logging page by: * marking more clearly that _asynchronous logging_ is not the solution to all performance problems. Depending on the case it could give all disadvantage of async processing without any measurable advantages. * removes the system properties and points to the appropriate "Configuration properties" section. * refreshes the configuration examples by adding an example for each of the configuration formats. Closes #2534.
ppkarwasz
added a commit
that referenced
this issue
May 15, 2024
We refresh the asynchronous logging page by: * marking more clearly that _asynchronous logging_ is not the solution to all performance problems. Depending on the case it could give all disadvantage of async processing without any measurable advantages. * removes the system properties and points to the appropriate "Configuration properties" section. * refreshes the configuration examples by adding an example for each of the configuration formats. Closes #2534.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As agreed in the site structure document, revamp the
Asynchronous loggingpage such thatasync.adocYieldingWaitStrategyissue shared in [2.17.1] AsyncLogger thread is stuck on 100% CPU on lmax-34. queue polling #2169 (comment)2.x, port tomainThe text was updated successfully, but these errors were encountered: