Well I've switched on to AspectJ load time weaving and was able to intercept calls on also the wicket Components methods. I've tested locally to see where are the missing numbers.
Seemed not much time was spent in onInitialize() afterall, the cause by the fact that even if the Services layer was intercepted, I did not think of the OpenEntityManagerInViewFilter which caused DB hits that were not going through the Service layer and thus not counted. 2. I was counting also the first hit of the first page which meant getMarkup calls for the components. That markup is then cached on subsequent calls but when called it does take it's toll. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Tracking-performance-issues-on-requests-best-practices-tp4657676p4657706.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
