Irena Shaigorodsky created WICKET-4591:
------------------------------------------
Summary: Sugnificant performance overhead encountered on wicket
page with 64 components
Key: WICKET-4591
URL: https://issues.apache.org/jira/browse/WICKET-4591
Project: Wicket
Issue Type: Bug
Affects Versions: 1.4.19
Environment: Windows Server 2008, JDK 1.6
Reporter: Irena Shaigorodsky
A custom page comprises totals 64 component render calls. The page takes 10138
ms to open as profiled with Java Profile for Eclipse.
Following hot spots were identified by profiles
Hot-spots
org.apache.wicket.proxy.LazyInitProxyFactory$JdkHandler.invoke() 3208ms
9 calls 356 ms/call
org.apache.wicket.util.resource.locator.ResourceStreamLocator.getResourceStream()
2891ms 52 calls 55 ms/call
org.apache.wicket.util.resource.locator.LocaleResourceNameIterator.next()
1310ms 24 calls 54.58 ms/call
org.apache.wicket.util.file.WebApplicationPath.find() 1167ms 16 calls
72.94 ms/call
org.apache.wicket.util.io.IObjectStreamFactory$DefaultObjectStreamFactory$2.writeObjectOverride()
306ms 2 calls 153ms/call
org.apache.wicket.Component.writeObject() 255ms 4 calls 63.75ms/call
org.apache.wicket.util.resource.locator.ResourceStreamLocator.locateByClassLoader()
118ms 54 calls 2.18 ms/call
Totaling 9255 ms spent in Wicket code and unacceptable performance. Can Wicket
support custom pages of that size? How the performance can be improved?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
