Repository navigation
feat(compile): memory statistics in -tstats - #1209
Merged
Merged
Conversation
`-tstats <file>` recorded, for each command of the compiled file, its
location and its time. It now also records, as `key=value` fields
after these two, its CPU time, the memory it allocated, the size and
the peak size of the major heap after it, and the number of major
collections during it:
1:0 7:23 0.083473 cpu=0.080641 alloc=133.550 heap=33.5 top=33.5 gc=1
Sizes are in MB. They come from `Gc.quick_stat`, which costs nothing
noticeable. The peak size of the major heap shows which commands make
a file need its memory, and the allocated memory measures the work of
a command independently of the load of the machine.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
-tstats <file>recorded, for each command of the compiled file, itslocation and its time. It now also records, as
key=valuefieldsafter these two, its CPU time, the memory it allocated, the size and
the peak size of the major heap after it, and the number of major
collections during it:
Sizes are in MB. They come from
Gc.quick_stat, which costs nothingnoticeable. The peak size of the major heap shows which commands make
a file need its memory, and the allocated memory measures the work of
a command independently of the load of the machine.