deardeng opened a new pull request, #66378:
URL: https://github.com/apache/doris/pull/66378

   Problem Summary: Cloud tablet route-cache rebuilding calls fillBeToTablets 
for current and future placements. The previous putIfAbsent calls eagerly 
constructed up to six candidate maps and sets for every placement even when the 
keys already existed, and then performed separate lookups. Use the containers 
returned by computeIfAbsent at every level and add a focused unit test that 
verifies all six container paths while preserving the global, table, and 
partition index contents.
   
   An isomorphic multi-scale JVM allocation model with 2 million entities, 
four-route fan-out, current/future passes, and three index scopes estimated 
cumulative allocation per modeled rebuild at 12.52 GiB before and 8.59 GiB 
after the change, saving 3.93 GiB (31.4%). For 4 million tablets, the fill-path 
cumulative-allocation reduction is expected to remain about 31% under 
comparable topology, while the absolute GiB saving depends on cluster and 
replica fan-out. The retained graph remained about 3.76 GiB and the peak proxy 
about 966 MiB, so this change does not claim a comparable steady-state heap or 
process-wide reduction. Timing samples were noisy, so no throughput improvement 
is claimed.
   
   ### Release note
   
   None
   
   ### Check List (For Author)
   
   - Test: Unit Test / Manual benchmark
       - ./run-fe-ut.sh --run 
org.apache.doris.cloud.catalog.CloudTabletRebalancerTest#testFillBeToTabletsUsesComputedContainers
       - cd fe && mvn checkstyle:check -pl fe-core
       - Multi-scale isomorphic JVM allocation model: 12.52 GiB to 8.59 GiB 
cumulative allocation per modeled rebuild
   - Behavior changed: No
   - Does this need documentation: No
   
   ### What problem does this PR solve?
   
   Issue Number: close #xxx
   
   Related PR: #xxx
   
   Problem Summary:
   
   ### Release note
   
   None
   
   ### Check List (For Author)
   
   - Test <!-- At least one of them must be included. -->
       - [ ] Regression test
       - [x] Unit Test
       - [ ] Manual test (add detailed scripts or steps below)
       - [ ] No need to test or manual test. Explain why:
           - [ ] This is a refactor/code format and no logic has been changed.
           - [ ] Previous test can cover this change.
           - [ ] No code files have been changed.
           - [ ] Other reason <!-- Add your reason?  -->
   
   - Behavior changed:
       - [x] No.
       - [ ] Yes. <!-- Explain the behavior change -->
   
   - Does this need documentation?
       - [x] No.
       - [ ] Yes. <!-- Add document PR link here. eg: 
https://github.com/apache/doris-website/pull/1214 -->
   
   ### Check List (For Reviewer who merge this PR)
   
   - [ ] Confirm the release note
   - [ ] Confirm test cases
   - [ ] Confirm document
   - [ ] Add branch pick label <!-- Add branch pick label that this PR should 
merge into -->
   
   


-- 
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