Closed
Bug 54715
Opened 24 years ago
Closed 24 years ago
replace indicies with string iterators in nsXULTemplateBuilder::ParseAttribute()
Categories
(Core :: XUL, defect, P3)
Core
XUL
Tracking
()
RESOLVED
FIXED
People
(Reporter: waterson, Assigned: waterson)
References
Details
(Keywords: perf)
Attachments
(1 file)
5.05 KB,
patch
|
Details | Diff | Splinter Review |
Currently, we use integer indicies to maintain our position in nsXULTemplateBuilder::ParseAttribute (because currenty, we can only create a Substring() using indicies). This requires us to make a ton of calls to CharAt(), and accounts for 26% of the time spent in ParseAttribute(). (That translates to about 2.5% of the overall time spent scrolling a mail threadpane, for example.) Replacing the index-based implementation with iterators will significantly reduce this cost.
Assignee | ||
Comment 1•24 years ago
|
||
Depends on iterator-based API for Substring()
Assignee | ||
Comment 2•24 years ago
|
||
Assignee | ||
Comment 3•24 years ago
|
||
Well, this wasn't the 2.5% speedup I was hoping for. In reality, we've just inlined a bunch of the work, so Quantify shows the time-in-function increases a bit, even though there is no time spent in CharAt() anymore. It's a small net win: about 1%. (Last cookie...fatness...)
Comment 4•24 years ago
|
||
r=scc :-)
Comment 5•24 years ago
|
||
a=hyatt
Assignee | ||
Comment 6•24 years ago
|
||
fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
You need to log in
before you can comment on or make changes to this bug.
Description
•