Avoid creating expensive Path objects in split creation code #24317
+99
−115
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.
Description
Avoid creating expensive Hadoop Path objects in split creation code. Path object creation is cpu intensive.
Motivation and Context
We observed that when coordinator is running hot, a good amount of CPU is being spent on Hadoop Path object creation. So we want to reduce that especially in split creation code path.
Impact
None
Test Plan
unit tests
Contributor checklist
Release Notes
Please follow release notes guidelines and fill in the release notes below.