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

   ### What problem does this PR solve?
   
   Issue Number: None
   
   Related PR: #65761
   
   Problem Summary:
   
   This forward-ports #65761 from `opt_perf_4.1` to `master`.
   
   Shuffle hash join build and probe operators run in separate pipelines, so 
their per-instance profiles are difficult to correlate. Add the fragment 
instance ID to both hash join build and probe custom profiles. Profiles with 
the same join node ID and `InstanceID` now identify the corresponding 
build/probe pair without relying on process-local hash table addresses.
   
   ### Release note
   
   None
   
   ### Check List (For Author)
   
   - Test
       - [ ] Regression test
       - [ ] Unit Test
       - [ ] Manual test
       - [x] No need to test or manual test. The change only adds profile 
metadata.
           - `build-support/clang-format.sh` (passed)
           - `build-support/check-format.sh` (passed)
           - `git diff --check origin/master...HEAD` (passed)
           - `BUILD_TYPE=ASAN ./build.sh --be` (attempted; CMake configured 
successfully, but Ninja was blocked before compilation because this worktree 
lacks `thirdparty/installed/lib64/liblance_c.a`)
           - `thirdparty/build-thirdparty.sh lance_c` (attempted; blocked 
because the required Rust/Cargo 1.91 toolchain is unavailable)
           - `build-support/run-clang-tidy.sh --base origin/master --build-dir 
be/build_ASAN` (attempted; blocked by the existing `core/types.h` unmatched 
`NOLINTEND` and missing system `stddef.h`; no diagnostic identified on the 
added lines)
   - [ ] This is a refactor/code format and no logic has been changed.
   - Behavior changed:
       - [ ] No.
       - [x] Yes. Hash join build and probe profiles include `InstanceID`.
   - Does this need documentation?
       - [x] No.
       - [ ] Yes.
   


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