Closed Bug 463962 Opened 16 years ago Closed 16 years ago

TM: Performance regression on string-tagcloud

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 464866

People

(Reporter: bzbarsky, Assigned: dmandelin)

Details

Comparing m-c nighty from today to m-c nightly from 2008-11-04, I see:

   tagcloud:  *1.35x as slow*   120.2ms +/- 2.5%  162.8ms +/- 2.4%  significant

I get similar numbers with my own tracemonkey build from today (the 160-ish number, not the 120-ish one).
Flags: blocking1.9.1?
Did the number of side exits increase?
Not sure.   This testing is all in an optimized mozilla.org nightly.
Assignee: general → dmandelin
We /think/ this is from increased cost of compiling regexes (it regressed when native regex landed). This should be confirmed.
Flags: blocking1.9.1? → blocking1.9.1+
Yes, we have verified this experimentally. Caching regular expressions based on the string instead of regexp object eliminates the slowdown.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.