You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 10, 2024. It is now read-only.
I haven't found a good comparison of blitz4j vs the new log4j2 async logger.
Can somebody give me a short answer if it is worth to change to blitz4j if I already have log4j2 in place.
I know blitz4j provides more features like handling log storms which comes very handy but from a scalability (less contention etc) pov I dont see a real reason (in fact I think log4j2 performs better because of the Disruptor).
Is this a reasonable statement?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I haven't found a good comparison of blitz4j vs the new log4j2 async logger.
Can somebody give me a short answer if it is worth to change to blitz4j if I already have log4j2 in place.
I know blitz4j provides more features like handling log storms which comes very handy but from a scalability (less contention etc) pov I dont see a real reason (in fact I think log4j2 performs better because of the Disruptor).
Is this a reasonable statement?
The text was updated successfully, but these errors were encountered: