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
The function Dispatcher.sinksFor() calculates the current set of sinks every time a log event is dispatched. This might be very inefficient with large numbers of log events.
Perhaps introduce a simple cache (map) of sinks, keyed by logger name. Considerations:
What if there is a very large number of logger names? Could the map grow very large? (YAGNI?)
How often might the configuration change? Level configurations can be changed by calling the config DSL in a running application. Perhaps introduce simple cache invalidation? (YAGNI?)
The text was updated successfully, but these errors were encountered:
The function
Dispatcher.sinksFor()
calculates the current set of sinks every time a log event is dispatched. This might be very inefficient with large numbers of log events.Perhaps introduce a simple cache (map) of sinks, keyed by logger name. Considerations:
The text was updated successfully, but these errors were encountered: