The perfomance I meant was (e.g. for methods): The standard MethodInvocation
used when running "non-optimzed" uses reflection to call the target method:
| public Object invokeNext() throws Throwable
| {
| ...
|
| //end of advice chain
| try
| {
| return method.invoke(getTargetObject(), arguments);
| }
| catch (InvocationTargetException e)
| {
| throw e.getTargetException();
| }
|
| }
|
Reflective calls are slower than "real" calls, which is why we in the
"optimized" version generate an interceptor tailor-made for that joinpoint,
which calls the target joinpoint properly, e.g:
| public Object invokeNext() throws Throwable
| {
| ...
|
| //end of advice chain
| try
| {
| return ((POJO)typedTargetObject).someMethod(arg1, arg2, arg3);
| }
| catch (InvocationTargetException e)
| {
| throw e.getTargetException();
| }
|
| }
|
The amount of classes loaded into memory should not be a hit on performance of
the jvm on a whole, but if the number is huge you might need to increase the
MaxPermSize of your jvm
http://www.unixville.com/~moazam/stories/2004/05/17/maxpermsizeAndHowItRelatesToTheOverallHeap.html
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3918175#3918175
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3918175
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
