API for creating and processing heap dumps fully in memory #341
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
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.
Wouldn't it be great if Heap dump data could be processed in memory, without the need to create anything on disk? Then it would be possible to analyze heap dumps in restricted environments, where access to disk is restricted. This PR is my attempt to provide such functionality.
Looks like the
HprofMappedByteBufferneeds the mmapped file only when constructing itself. Then it can operate over regularByteBuffer. Looks like the system is ready to work without the cache directory whenCacheDirectory.cacheDirectoryisnull.Adding one new API factory method that takes
ByteBufferinstead of theFile. SubclassingHeapTestand running the same tests in memory only mode.