Use new SegmentedList and SegmentedDictionary to process large heap dumps #1498
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.
These changes are a continuation of the following PRs:
In summary we are hooking everything together, and able to process large memory heap dumps. The actual changes are:
SerializationConfigurationinstance specifying if it should treatStreamLabelinstances as 32 or 64bit objects; as well as making the necessary adjustments to take advantage of this fact when processing a memory graph.XmlGcHeapDumpclass public for it to be used in the PerfView.Tests project.SegmentedDictionaryinstance since it is not that accurate and the range is subject to change if the internal implementation of aDictionarychanges.SegmentedMemoryStreamWriterinstance it creates is passed the correctStreamLabelsize information.