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
I profiled my application (on Wildfly 8) and I found that Logger.getLogger, in voldemort.store.routed.action.AbstractAction, imposes a significative overhead. I would recommend to set it as static to reduce this overhead
The text was updated successfully, but these errors were encountered:
Can you share your metrics ? Can you also share how long did you run the
tests and what is the get/put/getall/delete load you applied on the server
? Is this a single machine test or multi machine test ?
getLogger is supposed to return the cached instance and not create a new
one every time.
If you change this to static, then every instance of the log will show
AbstractAction, instead of the respective action which will confuse a lot
in logging.
So I want to weigh the pros and cons, before making any changes.
I profiled my application (on Wildfly 8) and I found that
Logger.getLogger, in voldemort.store.routed.action.AbstractAction,
imposes a significative overhead. I would recommend to set it as static
to reduce this overhead
—
Reply to this email directly or view it on GitHub #222.
I profiled my application (on Wildfly 8) and I found that Logger.getLogger, in voldemort.store.routed.action.AbstractAction, imposes a significative overhead. I would recommend to set it as static to reduce this overhead
The text was updated successfully, but these errors were encountered: