Revision: 6899
Author: [email protected]
Date: Tue Feb 22 07:04:25 2011
Log: --nocompress-log no more needed
http://code.google.com/p/v8/source/detail?r=6899
Modified:
/wiki/ProfilingChromiumWithV8.wiki
=======================================
--- /wiki/ProfilingChromiumWithV8.wiki Thu Sep 16 05:29:36 2010
+++ /wiki/ProfilingChromiumWithV8.wiki Tue Feb 22 07:04:25 2011
@@ -22,14 +22,6 @@
{{{
./Chromium --no-sandbox --js-flags="--logfile=%t.log --noprof-lazy
--prof-auto"
}}}
-
-or
-
-{{{
-./Chromium --no-sandbox --js-flags="--logfile=%t.log --noprof-lazy
--prof-auto --nocompress-log"
-}}}
-
-if you want to be able to parse logs with your eyes.
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.
@@ -39,8 +31,7 @@
* *--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;
- * *--nocompress-log* - disables log contents compression which makes
them unreadable for humans (but they still can be processed with V8's tick
processor scripts).
+ * *--prof-auto* - tells that CPU profiling should start immediately
after V8 initialization.
== Notes ==
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
