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
Is it possible to publish architecture diagram for this library? I want to understand how various components like rate limiter, filter are related to each other.
Also it has been written that flogger is more performant than other logging libraries present. Can you please publish benchmarks and assumptions? Considering changing from existing logging lib to flogger is a big effort(unlike changing from lets say log4j to log4j2), looking at benchmark will help us understand whether the benefits are relevant to us or not (for example it might be performing very well when log statements are disabled, but equally good when all the logs are enabled. In this scenario if an application does not have too much filtering use case it might not get any benefit moving from log4j to flogger)
thanks
The text was updated successfully, but these errors were encountered:
Hi Team,
Is it possible to publish architecture diagram for this library? I want to understand how various components like rate limiter, filter are related to each other.
Also it has been written that flogger is more performant than other logging libraries present. Can you please publish benchmarks and assumptions? Considering changing from existing logging lib to flogger is a big effort(unlike changing from lets say log4j to log4j2), looking at benchmark will help us understand whether the benefits are relevant to us or not (for example it might be performing very well when log statements are disabled, but equally good when all the logs are enabled. In this scenario if an application does not have too much filtering use case it might not get any benefit moving from log4j to flogger)
thanks
The text was updated successfully, but these errors were encountered: