On Thu, Mar 5, 2009 at 4:40 PM, Rickard Öberg <[email protected]> wrote: > Stuart McCulloch wrote: >> With CGLIB one essentially creates a proxy that holds one invoker per >> method, so when the invoker is called you know exactly which method is >> being dispatched. The invoker holds on to the CompositeMethodModel, and >> so no lookup whatever is done... faaaast... >> >> >> +1 will much better (and faster) > > I did a test with this, and so far the change cranked up the plain mixin > invocation performance from about 5.5M/s to 8.5M/s on my machine. It's > not a huge increase, and the code becomes invaded with CGLIB quite a > lot, so I'm not sure it's worth it. But if we want to, this is the > increase we'd get.
And if it is a larger invocation stack the benefit will diminish? Cheers Niclas -- http://www.qi4j.org - New Energy for Java _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
