[meta]Slow performance on this DOM manipulation testcase

RESOLVED INCOMPLETE

Status

Core Graveyard
Tracking
RESOLVED INCOMPLETE
8 years ago
10 months ago

People

(Reporter: bz, Unassigned)

Tracking

({meta, perf})

Trunk
x86
Mac OS X
meta, perf

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

Created attachment 385180 [details]
Testcase

We're a lot slower than Safari 4 on all three parts of the testcase linked in the url field (and attached, with a doProfile boolean to flip to true if you want to shark it).

We're spending a bunch of time in JS_ComputeThis, xpc_qsXPCOMObjectToJsval.  Those two account for over 30% of the runtime for the "node creation" approaches.  Also spending a fair amount of time on the final insert; in the innerHTML testcase this is 70+% of total time.  We should use this bug as the tracker and file separate bugs on specific issues here, or add as deps bugs that are likely to help (e.g. slimwrapper).
Some profiles:
http://web.mit.edu/bzbarsky/www/profiles/bug500489/

Updated

8 years ago
Depends on: 482788
Keywords: perf

Comment 2

3 years ago
Nightly / Chrome 32 / IE 11

Straight-forward node creation 0.413s / 0.365s / 3.034s
Straight-forward node creation, but no lastChild.lastChild 0.392s / 0.207s / 2.884s
Using innerHTML instead 0.3s / 0.278s / 5.339s

Comment 3

10 months ago
Marking all tracking bugs which haven't been updated since 2014 as INCOMPLETE.
If this bug is still relevant, please reopen it and move it into a bugzilla component related to the work
being tracked. The Core: Tracking component will no longer be used.
Status: NEW → RESOLVED
Last Resolved: 10 months ago
Resolution: --- → INCOMPLETE
(Assignee)

Updated

10 months ago
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.