You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Juergen Donnerstag (JIRA)" <ji...@apache.org> on 2010/11/20 14:58:15 UTC
[jira] Closed: (WICKET-1671) Performance problem with detach
(Component.isAuto)
[ https://issues.apache.org/jira/browse/WICKET-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juergen Donnerstag closed WICKET-1671.
--------------------------------------
Resolution: Cannot Reproduce
Please provide more evidence.
> Performance problem with detach (Component.isAuto)
> --------------------------------------------------
>
> Key: WICKET-1671
> URL: https://issues.apache.org/jira/browse/WICKET-1671
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.3.3
> Environment: Tomcat 5.5.23
> Windows XP/JDK 1.6.0_03
> Windows 2003/JDK 1.5
> Reporter: Heikki Uotinen
> Assignee: Johan Compagner
> Attachments: detach.zip, wicket-1671
>
>
> We have an application that uses AjaxSelfUpdatingTimerBehavior to update a panel that has several child components.
> Application has a performance problem and profiler shows that the most time is consumed in Component.isAuto method.
> It seems that isAuto flag is checked up and down the component tree.
> There is attached a simple demonstration about the problem and screenshots of the profiler displays.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.