[Webkit-unassigned] [Bug 97270] DOM-in-JavaScript performance experiments

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Sep 26 15:02:52 PDT 2012


https://bugs.webkit.org/show_bug.cgi?id=97270





--- Comment #16 from Adam Barth <abarth at webkit.org>  2012-09-26 15:03:19 PST ---
> Here are some results I got:

Fascinating.

> That looks like the JS-based version is about 50% slower, not 30% faster. Am I misunderstanding the test or what the claim was?

Here are the numbers I got (five minutes ago) with DumpRenderTree in the chromium port:

$ ./out/Release/DumpRenderTree file:///src/abarth-webkit/PerformanceTests/Dromaeo/dom-traverse.html

== js ==

avg 326188 runs/s
median 0 runs/s
stdev 1218.1536848854498 runs/s
min 325071 runs/s
max 328243 runs/s

== cpp ==

avg 266485.3966033966 runs/s
median 0 runs/s
stdev 671.5778183390692 runs/s
min 265506 runs/s
max 267288.48851148854 runs/s

That shows the JS implementation running faster than the CPP implementation.  I need re-run these tests on a Mac to compare the absolute numbers between JSC and V8.

We might be getting different outcomes here because there are two moving pieces:

1) The performance of the JSC and the V8 bindings code.
2) The performance of the underlying JavaScript engine.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the webkit-unassigned mailing list