Description
We should profile Wicket and search for (and fix) new bottlenecks we may have introduced since 1.2. We should give memory consumption a very good look and see if there is still room for optimizing.
Attachments
Issue Links
- incorporates
-
WICKET-792 Calls to getString() are sloooooow.
- Resolved