[LuaJIT] jit.p: Enhance 'v' profiler mode #621
Merged
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 change prints more information when profiling at trace granularity. The idea is to make it easier to audit the runtime behavior of your apps: how many traces do they compile into, how are those traces connected together, and which execution path does each trace represent.
This PR builds on #619 and contains the code previously described in issue #611.
More detail with examples:
Previously the 'v' mode would print a terse summary. For example when profiling the rate_limiter app selftest:
More information is shown with this change:
This tells us:
Note that it is also possible to combine this profile mode with line based profiling to have more visibility into what is happening inside traces: