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.
Thank
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.
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
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. :)
Yeah, for sure. Which tool are you using? We are
Me too :)... YourKit rocks! :)
Eelco Hillenius wrote:
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
Eelco, the ISessionStore interface has a lot of methods.. can you give me an
example of how to get rid of the serialization? It really slows down the
application.
I can imagine those checks did cost something in 1.2, though with Wicket 1.3
and the way we use it with the session stores should
On 8/14/07, Alex Objelean [EMAIL PROTECTED] wrote:
In wicket-1.2.6 I used this in order to not serialize session attributes:
[CODE]
getDebugSettings().setSerializeSessionAttributes(false);
[/CODE]
What is equivalent for this in wicket-1.3.0-beta2?
Thank you!
There is none, but if you
On 8/14/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
On 8/14/07, Alex Objelean [EMAIL PROTECTED] wrote:
In wicket-1.2.6 I used this in order to not serialize session attributes:
[CODE]
getDebugSettings().setSerializeSessionAttributes(false);
[/CODE]
What is equivalent for this in
