Last Comment Bug 500489 - [meta]Slow performance on this DOM manipulation testcase
: [meta]Slow performance on this DOM manipulation testcase
: meta, perf
Product: Core Graveyard
Classification: Graveyard
Component: Tracking (show other bugs)
: Trunk
: x86 Mac OS X
-- normal with 1 vote (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
: chris hofmann
Depends on: slimwrapper
  Show dependency treegraph
Reported: 2009-06-25 12:54 PDT by Boris Zbarsky [:bz] (still a bit busy)
Modified: 2016-07-15 12:13 PDT (History)
10 users (show)
See Also:
QA Whiteboard:
Iteration: ---
Points: ---

Testcase (4.75 KB, application/xhtml+xml)
2009-06-25 12:54 PDT, Boris Zbarsky [:bz] (still a bit busy)
no flags Details

Description User image Boris Zbarsky [:bz] (still a bit busy) 2009-06-25 12:54:01 PDT
Created attachment 385180 [details]

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).
Comment 1 User image Boris Zbarsky [:bz] (still a bit busy) 2009-06-25 13:03:52 PDT
Some profiles:
Comment 2 User image Guilherme Lima 2014-02-23 13:54:16 PST
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 User image BMO Automation 2016-07-01 13:04:04 PDT
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.

Note You need to log in before you can comment on or make changes to this bug.