You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Enhance the performance of ABFS Driver for write-heavy workloads by improving concurrency within writes.
The proposed design advocates for a centralized WriteThreadPoolSizeManager class to handle the collective thread allocation required for all write operations across the system, replacing the current CachedThreadPool in AzureBlobFileSystemStore. This centralized approach ensures that the initial thread pool size is set at 4 * number of available processors and dynamically adjusts the pool size based on the system's current CPU utilization. This adaptive scaling and descaling mechanism optimizes resource usage and responsiveness. Moreover, this shared thread pool is accessible and utilized by all output streams, streamlining resource management and promoting efficient concurrency across write operations.
hadoop-tools/hadoop-azure generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)
+1 💚
shadedclient
20m 18s
patch has no errors when building and testing our client artifacts.
_ Other Tests _
+1 💚
unit
2m 19s
hadoop-azure in the patch passed.
+1 💚
asflicense
0m 23s
The patch does not generate ASF License warnings.
77m 36s
Reason
Tests
SpotBugs
module:hadoop-tools/hadoop-azure
org.apache.hadoop.fs.azurebfs.WriteThreadPoolSizeManager.adjustThreadPoolSizeBasedOnCPU(double) does not release lock on all exception paths At WriteThreadPoolSizeManager.java:on all exception paths At WriteThreadPoolSizeManager.java:[line 268]
anmolanmol1234
changed the title
HADOOP-19472: [ABFS][Improve write workload performance for ABFS]
HADOOP-19472: [ABFS] Improve write workload performance for ABFS by efficient concurrency utilization
May 7, 2025
hadoop-tools/hadoop-azure generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)
+1 💚
shadedclient
22m 6s
patch has no errors when building and testing our client artifacts.
_ Other Tests _
+1 💚
unit
2m 20s
hadoop-azure in the patch passed.
+1 💚
asflicense
0m 25s
The patch does not generate ASF License warnings.
78m 44s
Reason
Tests
SpotBugs
module:hadoop-tools/hadoop-azure
org.apache.hadoop.fs.azurebfs.WriteThreadPoolSizeManager.adjustThreadPoolSizeBasedOnCPU(double) does not release lock on all exception paths At WriteThreadPoolSizeManager.java:on all exception paths At WriteThreadPoolSizeManager.java:[line 263]
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.
Enhance the performance of ABFS Driver for write-heavy workloads by improving concurrency within writes.
The proposed design advocates for a centralized
WriteThreadPoolSizeManager
class to handle the collective thread allocation required for all write operations across the system, replacing the current CachedThreadPool in AzureBlobFileSystemStore. This centralized approach ensures that the initial thread pool size is set at4 * number of available processors
and dynamically adjusts the pool size based on the system's current CPU utilization. This adaptive scaling and descaling mechanism optimizes resource usage and responsiveness. Moreover, this shared thread pool is accessible and utilized by all output streams, streamlining resource management and promoting efficient concurrency across write operations.