It may be possible (but a bit of a hack) to use async loggers without
reflection. It involves compiling your own version of the
com.lmax.disruptor.util.Util class where you replace the implementation of the
#getUnsafe() method with a simple call to sun.misc.Unsafe.getUnsafe().
Obviously this is
, July 30, 2013 10:14 AM
To: Log4J-Users List
Subject: Re: reflection? RE: async logger on slow single core env performs 50%
worse than log4j v1
It may be possible (but a bit of a hack) to use async loggers without
reflection. It involves compiling your own version of the
com.lmax.disruptor.util.Util
Hi guys, I mentioned this observation last week, that my embedded single core
env, the VM also does not support reflection. Is reflection used in the hot
path of logging that might be affecting my testing of V2 using more CPU than v1?
LOGGER.debug(sun.reflect.Reflection is not installed);
In your environment I would definitely recommend using BasicContextSelector as
you are unlikely to have need for multiple LoggerContexts.
Ralph
On Jul 29, 2013, at 7:08 AM, SMITH, CURTIS wrote:
Hi guys, I mentioned this observation last week, that my embedded single
core env, the VM also
This probably warrants an enhancement to Log4jContextFactory. I can imagine
other use cases where defaulting to BasicContextSelector also makes sense.
Ralph
On Jul 29, 2013, at 8:02 AM, Ralph Goers wrote:
In your environment I would definitely recommend using BasicContextSelector
as you are
)
at
java.security.AccessController.doPrivileged(AccessController.java:255)
... 40 more
-Original Message-
From: Ralph Goers [mailto:ralph.go...@dslextreme.com]
Sent: Monday, July 29, 2013 11:05 AM
To: Log4J Users List
Subject: Re: reflection? RE: async logger on slow single core env
29, 2013 11:05 AM
To: Log4J Users List
Subject: Re: reflection? RE: async logger on slow single core env performs
50% worse than log4j v1
This probably warrants an enhancement to Log4jContextFactory. I can imagine
other use cases where defaulting to BasicContextSelector also makes sense
...@dslextreme.com]
Sent: Monday, July 29, 2013 11:05 AM
To: Log4J Users List
Subject: Re: reflection? RE: async logger on slow single core env performs
50% worse than log4j v1
This probably warrants an enhancement to Log4jContextFactory. I can imagine
other use cases where defaulting
29, 2013 2:15 PM
To: Log4J Users List
Subject: Re: reflection? RE: async logger on slow single core env performs
50% worse than log4j v1
Yes. ClassLoaderContextSelector is complicated and probably not at all what
you want. it uses the Sun reflection class, which you've noticed
