Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for other (non-V8) trace formats #3

Open
5 tasks
mourner opened this issue Apr 2, 2018 · 2 comments
Open
5 tasks

Add support for other (non-V8) trace formats #3

mourner opened this issue Apr 2, 2018 · 2 comments
Labels
enhancement New feature or request

Comments

@mourner
Copy link
Member

mourner commented Apr 2, 2018

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?

cc @springmeyer

@mourner mourner added the enhancement New feature or request label Apr 2, 2018
@rebornix
Copy link

rebornix commented Apr 3, 2018

I'll suggest to support the output of Chrome Dev Tools JavaScript Profiling.

@mourner
Copy link
Member Author

mourner commented Apr 3, 2018

@rebornix good idea, added to the list. Code for parsing it (for reference): https://github.com/bengl/cpuprofile2stackcollapse/blob/master/index.js

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants