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

[bugzilla-daemon at webkit.org]

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





--- Comment #17 from Maciej Stachowiak <mjs at apple.com>  2012-09-26 16:02:26 PST ---
(In reply to comment #16)
> > 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.

I will try to rearrange the test to be a single file and print both results, so it can easily be loaded in different browsers. Because I'm also curious what the results are in different versions. And that is probably easier for me than building chromium webkit.

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