Using custom data structure for callstack tracking #2630
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.
@andimarek @bbakerman hello :)
I would like to propose the following optimization in
FieldLevelTrackingApproach. By using a custom data structure (a glorified int[] array), it is possible to gain some performance.I wrote 2 performance tests:
IntMapBenchmark(included in the PR) on my machine, I get 5x better performance:Output:
please have a look and let me know... I really don't like the current name as it is not a real replacement for a
Map<Integer, Integer>! :-)