On 2012/11/29 15:56:30, abarth wrote:
On 2012/11/29 08:26:33, Sven Panne wrote:
> How exactly did you profile this? I'd be interested in trying out some
things,
> but I don't have a black belt in profiling Chrome as a whole yet... :-)
1) Build the Chromium port of WebKit for Linux:
https://trac.webkit.org/wiki/Chromium
2) sudo apt-get install google-perftools
3) ./Tools/Scripts/run-perf-tests Dromeo/dom-traverse.html --profile
The --profile option is very new, so it might still have some rough
edges. If
you want backtraces, you might need to run "update-webkit --chromium" and
"build-webkit --chromium" with GYP_DEFINES="profiling=1" in your
environment,
but basic profiling should work without that.
To profile on Mac OS X, you need to export
GYP_DEFINES="mac_strip_release=0"
instead of profiling to get symbols in your build. You can then use
Instruments
(which comes with Xcode) to profile DumpRenderTree as you would any other
executable.
I recently landed a CL that hooks VMState to catch places where we call into
DOM, for profiling purposes. It would be bad if those state changes are
removed
entirely. Would it be possible to log state changes only when profiling
flags
are set so that for profiling, I can still rely on those state changes, but
for
the usual case, we could do away with the atomic increment and decrement?
https://codereview.chromium.org/11361275/
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
