[LuaJIT] jit.p: Add support for profiling at trace granularity #619
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is a patch written by Mike Pall that makes the profiler "v"
option report the time used by each trace separately. This can be used
to decide which traces to analyze when profiling large programs.
Example:
$ ./luajit -jp=v ../test.lua
47% TRACE 1
43% TRACE 2
6% Interpreted
3% Garbage Collector
Originally posted by Mike on the LuaJIT mailing list:
https://www.freelists.org/post/luajit/Profile-at-trace-granularity,1
This was referenced Sep 14, 2015
lukego
added a commit
to lukego/snabb
that referenced
this pull request
Sep 14, 2015
dpino
added a commit
to dpino/snabb
that referenced
this pull request
Dec 7, 2016
Store pid as a string
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a patch written by Mike Pall that makes the profiler "v"
option report the time used by each trace separately. This can be used
to decide which traces to analyze when profiling large programs.
Example:
Originally posted by Mike on the LuaJIT mailing list:
https://www.freelists.org/post/luajit/Profile-at-trace-granularity,1