Well, in this case the bottleneck was caused by an expensive call which was not cashed inside a very long list... Anyway, profiling tools helps very much in such cases, so I would recommend everybody who have performance issues to use it. :)
Eelco Hillenius wrote: > >> Eelco, you're right! >> The latest profiling shows where the bottleneck is... it is indeed not >> where >> I was looking for. >> I thought it was because of serialization because when using 1.2.x branch >> i >> found out that setSerializeSessionAttributes(false) improved a lot >> application responsiveness. > > Pfew. I (and the rest of the team) will sleep much better now ;-) > > Anything you want to share what your problem was in case people can > learn from it? > > Cheers, > > Eelco > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/setSerializeSessionAttributes-in-wicket-1.3.0-beta2-tf4267003.html#a12185336 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
