rich7420 opened a new pull request, #11123:
URL: https://github.com/apache/ozone/pull/11123

   ## What changes were proposed in this pull request?
   
   Recon full reprocess tasks repeatedly resolve worker-local accumulation maps 
through a shared concurrent map for every key. The OBS namespace summary task 
also performs RocksDB bucket-table point reads for every key, even when 
consecutive keys belong to the same bucket.
   
   This change:
   
   * caches OBS bucket metadata per worker and reuses the cached bucket object 
ID;
   * uses ThreadLocal worker accumulation maps while retaining a concurrent 
registry for final merging and flushing;
   * applies the worker-map optimization to namespace summary, container-key 
mapping, and file-size count reprocess paths;
   * adds regression coverage for the OBS bucket lookup count.
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-16281
   
   ## How was this patch tested?
   
   * Relevant Recon unit tests: 29 tests passed across 
TestNSSummaryTaskWithOBS, TestNSSummaryTaskWithFSO, TestContainerKeyMapperTask, 
and TestFileSizeCountTask.
   * The new regression test fails against upstream/master with 10 bucket-table 
lookups instead of the expected 2, and passes with this patch.
   * Full project checkstyle passed.
   * Full project PMD passed.
   * [10 x 10 
flaky-test-check](https://github.com/rich7420/ozone/actions/runs/32956562461): 
100/100 passed after retrying one Maven Central HTTP 403 infrastructure failure.
   * A local before/after task-level benchmark used 100,000 OBS keys across two 
buckets, two warmups, and five measured runs, repeated in reverse order. Median 
reprocess time decreased from 2098/2109 ms on upstream/master to 1598/1548 ms 
with this patch (24-27% lower), while throughput improved by 31-36%.
   
   Generated-by: Codex (GPT-5)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to