So I disabled CPU throttling as Dan suggested and ran full Dromaeo DOM Core
test
suite using src/tools/perf/run_measurement three times with each of the
following builds:
1) With patch set #9: generated assembly code checks if profiler is enabled
and
calls the callback directly as before if not.
2) With patch set #8: always call intermediate function that changes VM
state.
3) Without any changes.
On my z620 Linux desktop I've got the following results:
// ----------- with patch set #9(check in generated code)
-------------------
*RESULT dom: dom= 2288.3080499870944 runs/s
*RESULT dom: dom= 2192.0581529196734 runs/s
*RESULT dom: dom= 2298.401560011703 runs/s
// ----------- with patch set #8(always change state) -------------------
*RESULT dom: dom= 2267.9035800297943 runs/s
*RESULT dom: dom= 2267.279220577068 runs/s
*RESULT dom: dom= 2208.5243745011767 runs/s
// ----------- without patch -------------------
*RESULT dom: dom= 2238.9526837659027 runs/s
*RESULT dom: dom= 2293.108281884979 runs/s
*RESULT dom: dom= 2276.855695120652 runs/s
These results do not reveal any regression that would be noticeable with the
given level of noise. Based on that I propose to land patchset #8 and watch
golem results.
https://codereview.chromium.org/16286016/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
