[SPARK-53022][TESTS] Add MemoryConsumerBenchmark #51728
Open
+106
−0
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.
What changes were proposed in this pull request?
Adds a
MemoryConsumerBenchmark
and several cases for the basic allocation / free APIs.Why are the changes needed?
We once noticed that massive off-heap memory allocation calls to Spark’s memory APIs could slow down executions in our 3rd plugin. Adding a benchmark could help measuring the performance of the memory allocation API, and possibly help with improving performance of the memory code in the future.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
This is a patch to add a benchmark.
Was this patch authored or co-authored using generative AI tooling?
No.