USC02VH18LHV2R:UI sd158rp$ node --prof-process --preprocess -j isolate-0x102801e00-v8.log | flamebearer
ReferenceError: printErr is not defined
at TickProcessor.printError (evalmachine.<anonymous>:2770:3)
at TickProcessor.LogReader.processLog_ (evalmachine.<anonymous>:2522:12)
at TickProcessor.LogReader.processLogLine (evalmachine.<anonymous>:2405:10)
at TickProcessor.processLogFile (evalmachine.<anonymous>:2798:10)
at NativeModule.compile (bootstrap_node.js:613:7)
at Function.NativeModule.require (bootstrap_node.js:558:18)
at startup (bootstrap_node.js:150:20)
Invalid input; expected a V8 log in JSON format. Produce one with:
node --prof-process --preprocess isolate*.log
I think this:
Thanks for writing this, by the way!
I'm using this as reference for importing v8 logs into speedscope (https://github.com/jlfwong/speedscope)
I don't know where else to ask, so hopefully this is ok to post here :)
I don't understand exactly what the advantage of this project (or `0x` for that matter) is over Chrome's profiler, would you care to elaborate?
would a PR be welcome for this?
I'm thinking of adding a screenshot like this:
<img width="1280" alt="screen shot 2018-05-10 at 9 38 03 am" src="https://user-images.githubusercontent.com/6374832/39881469-e8d0c652-5435-11e8-887d-6d5e2160640b.png">
Not sure if you've seen this, netflix open sourced a similar tool today.
The heatmap overview is really compelling, thought I'd leave it here as an idea.
I might even take a stab at it if I get time... maybe 😝
In theory, it shouldn't be much of a trouble to add support for other trace formats. The common ones I've seen are:
- [ ] Perf traces (`perf report`)
- [ ] DTrace ticks
- [ ] FlameGraph folded traces (BCC, FlameGraph `stackcollapse`)
- [ ] Perf folded traces (`perf report -g folded` on Linux v4.5+)
- [ ] `cpuprofile` format used by Chrome Dev Tools?