Revision: 19879
Author: [email protected]
Date: Thu Mar 13 08:18:23 2014 UTC
Log: Edited wiki page ProfilingChromiumWithV8 through web user
interface.
http://code.google.com/p/v8/source/detail?r=19879
Modified:
/wiki/ProfilingChromiumWithV8.wiki
=======================================
--- /wiki/ProfilingChromiumWithV8.wiki Tue Feb 22 15:04:25 2011 UTC
+++ /wiki/ProfilingChromiumWithV8.wiki Thu Mar 13 08:18:23 2014 UTC
@@ -20,7 +20,7 @@
Here is how to run Chromium in order to get a CPU profile from the start
of the process:
{{{
-./Chromium --no-sandbox --js-flags="--logfile=%t.log --noprof-lazy
--prof-auto"
+./Chromium --no-sandbox --js-flags="--logfile=%t.log --prof"
}}}
Please note that you wouldn't see profiles in Developer Tools, because all
the data is being logged to a file, not to Developer Tools.
@@ -30,8 +30,7 @@
* *--no-sandbox* - turns off the renderer sandbox, obviously must have;
* *--js-flags* - this is the containers for flags passed to V8:
* *--logfile=%t.log* - specifies a name pattern for log files; *%t*
gets expanded into current time in milliseconds, so each process gets its
own log file; you can use prefixes and suffixes if you want, like this:
*prefix-%t-suffix.log*;
- * *--noprof-lazy* - allows shared libraries entries to be logged upon
CPU profiler initialization;
- * *--prof-auto* - tells that CPU profiling should start immediately
after V8 initialization.
+ * *--prof* - tells V8 to write statistical profiling information into
the log file.
== Notes ==
--
--
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/d/optout.
