Leverage the existing system-analyzer log processing and build a cli
around it with basic json output and filtering.
- Add v8-logviewer as a better cli to v8.log
- list scripts, functions, code objects, ics, deopts
- filter by script, function name...
- Add tools/find-d8.sh helper that we can use in all tools entry scripts
Todos:
- Add profile support (this is somewhat handled by the various
tick-processor helpers)
- Add more detailed output for each subcommand
- Long-term we want to probably replace this with a trace-processor
based solution that works seamlessly with data from d8 and from
chromium.
Change-Id: I5e0a13ab861ce33f88e7bab10ae2bd58a009292f
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7785576
Commit-Queue: Camillo Bruni <cbruni@chromium.org>
Auto-Submit: Camillo Bruni <cbruni@chromium.org>
Reviewed-by: Leszek Swirski <leszeks@chromium.org>
Commit-Queue: Leszek Swirski <leszeks@chromium.org>
Cr-Commit-Position: refs/heads/main@{#106846}
From the log data generated with --log-function-events we can create a
detailed model of a function's lifetime. The parse processor displays
several stats at a given time (percent and count) on a per function or
byte basis:
- preparsing
- parsing
- eager/lazy compiling
- execution
Bug: chromium:757467
Change-Id: I0ad5c9369c6a0628704e3caffb3920444ea603a9
Reviewed-on: https://chromium-review.googlesource.com/758641
Commit-Queue: Camillo Bruni <cbruni@chromium.org>
Reviewed-by: Mathias Bynens <mathias@chromium.org>
Cr-Commit-Position: refs/heads/master@{#50234}
Camillo Bruni
Yang Guo