I was profiling today with jvisualvm application that heavily uses lambdaj. I did not see any performance problems with it. We studied more and saw, that it is reaaaallly slooooow. (we have tens of thousands of elements in lists).
How come jvisualvm did not show me real execution times of lambdaj? After making start/stop timers to the code we saw the problem. Something to do with dynamic proxy/reflection?
Or was i just blind as a bat.
www-application: Wicket 1.4 (lot's of ajax) + LamdaJ + Guice
SCJP 5.0, SCJD URLyBird 1.3.3, OCMJEA 5 (SCEA) Factory Homes