InjectorImpl Performance [message #894827] |
Tue, 10 July 2012 16:49 |
|
I am still working to fully understand the DI engine, but as I was reviewing the code I noticed that the class (InjectorImpl) is not declared as final. Is there a reason that it is not declared as final? Wouldn't there be a performance increase if it were because the compiler could "in-line" the code?
[Note to self: read "Java Performance"]
[Updated on: Tue, 10 July 2012 16:55] Report message to a moderator
|
|
|
|
Re: InjectorImpl Performance [message #894853 is a reply to message #894851] |
Tue, 10 July 2012 19:17 |
|
Brian-
I'll give it a try, hopefully sometime this weekend I can have results. (Tonight I need to work on the PerspectiveSwitcher!)
Are there any existing performance tests for the framework?
I see the standard unit-tests, but there aren't any performance tests.
The other thing I would be interested in knowing is if the "HotSpot" JVM is doing its job and actually compiling down the bytecode. If methods are too long, the JVM will keep the method as bytecode even if it is a "hot" method. The issue is that longer methods are more difficult for the JVM to understand and optimize (to put it simply). Unfortunately, there is no single definition of a "long" method.
I might need some help in thinking up the logic for any performance tests, if none are presently available. But then I can look at both finalization and compilation of the different methods and see if anything makes a difference.
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03643 seconds