You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Sean Patrick Floyd (JIRA)" <ji...@apache.org> on 2009/02/25 12:36:01 UTC
[jira] Updated: (WICKET-2127) Javascript function Wicket.replaceAll
is unbearably slow
[ https://issues.apache.org/jira/browse/WICKET-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Patrick Floyd updated WICKET-2127:
---------------------------------------
Attachment: wicketReplaceAll.js
Using this version of Wicket.replaceAll changed the performance dramatically.
Now the FireBugs Profiler says the script takes up 1.98% of the processing time as opposed to ~60%
Sean
> Javascript function Wicket.replaceAll is unbearably slow
> --------------------------------------------------------
>
> Key: WICKET-2127
> URL: https://issues.apache.org/jira/browse/WICKET-2127
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4-RC2
> Environment: Firefox 3.0.5, Opera 9.2 (windows)
> Reporter: Sean Patrick Floyd
> Fix For: 1.4-RC3
>
> Attachments: wicketReplaceAll.js
>
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> I use AbstractAjaxTimerBehavior to update many different components on my pages periodically.
> After a while, the browser occupies 50% or more of the system resources.
> I used the javascript profiler in firebug and found that Wicket.replaceAll is responsible for 60+ percent of javascript processing time.
> The problem is that sequential string processing is used instead of much faster regular expressions
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.