[
https://issues.apache.org/jira/browse/WICKET-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678927#action_12678927
]
kan.izh edited comment on WICKET-2127 at 3/4/09 1:25 PM:
--------------------------------------------------------------------
Also
function removeIframeMark(text) {
var markerRe = new RegExp(marker, "g") //this variable could be cached
somewhere globally, so we could avoid regex compilation every time if it
affects performance
return text.replace(markerRe, "")
}
Wicket.decode1 = function(text) {
return text.replace(/\]\^/g, "]")
}
was (Author: kan.izh):
Also
function removeIframeMark(text) {
var markerRe = new RegExp(marker, "g") //this variable could
be cached somewhere globally, so we could avoid regex compilation if it affects
performance
return text.replace(markerRe, "");
}
> 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
> Assignee: Matej Knopp
> 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.
