Repository navigation
Report allocation, GC pauses and retained heap - #39
Merged
Merged
Conversation
Each workload stores the bytes allocated and the GC count and pause time over its timed section. After ingest the run forces a full GC and records the heap the loaded store keeps, minus a baseline taken before it opened.
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.
Closes #31
Every workload now records, over its timed section:
getTotalThreadAllocatedBytes)GarbageCollectorMXBean; with ParallelGC that's stop-the-world time)After ingest the run forces a full GC and records the heap the loaded store keeps. A baseline taken before the store opens is subtracted, so the dataset arrays both runs share aren't counted.
The Resources table from #38 gains allocated-per-operation and GC pause rows. Rows where both stores paused 0 ms are left out. Old result files still render unchanged.
Smoke run at scale 1, async, one run each:
ingest.edgesand 0.9 s duringreopen. HyperGraphDB's pauses are spread out and smaller.read.incidence,read.comembership, cold reads). Oningest.edgesand single commits it allocates 2.5 times more.