Skip to content

Conversation

@zhaorongsheng
Copy link
Contributor

@zhaorongsheng zhaorongsheng commented Oct 27, 2025

What problem does this PR solve?

Issue Number: close #57367

Related PR: #xxx

Problem Summary:

Release note

None

Check List (For Author)

  • Test

    • Regression test
    • 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
  • Behavior changed:

    • No.
    • Yes.
  • Does this need documentation?

    • No.
    • Yes.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

@hello-stephen
Copy link
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@zhaorongsheng
Copy link
Contributor Author

run buildall

@zhaorongsheng
Copy link
Contributor Author

run buildall

@doris-robot
Copy link

ClickBench: Total hot run time: 29.02 s
machine: 'aliyun_ecs.c7a.8xlarge_32C64G'
scripts: https://github.com/apache/doris/tree/master/tools/clickbench-tools
ClickBench test result on commit 65001b7485725ce1144c62338ae1bdad80e190b7, data reload: false

query1	0.06	0.06	0.05
query2	0.10	0.06	0.06
query3	0.26	0.10	0.10
query4	1.61	0.13	0.13
query5	0.31	0.28	0.30
query6	1.22	0.66	0.68
query7	0.05	0.03	0.03
query8	0.07	0.04	0.05
query9	0.66	0.55	0.56
query10	0.62	0.62	0.62
query11	0.19	0.14	0.14
query12	0.18	0.14	0.14
query13	0.64	0.62	0.61
query14	1.07	1.04	1.03
query15	0.89	0.91	0.91
query16	0.42	0.43	0.44
query17	1.16	1.21	1.14
query18	0.24	0.23	0.22
query19	2.00	1.91	1.93
query20	0.01	0.02	0.01
query21	15.36	0.23	0.17
query22	4.94	0.09	0.05
query23	15.61	0.32	0.11
query24	2.22	0.74	0.33
query25	0.08	0.07	0.07
query26	0.17	0.17	0.15
query27	0.07	0.07	0.06
query28	3.92	1.19	0.95
query29	12.59	4.62	3.77
query30	0.30	0.16	0.15
query31	2.83	0.68	0.42
query32	3.25	0.60	0.49
query33	3.20	3.08	3.16
query34	15.96	5.27	4.57
query35	4.67	4.66	4.64
query36	0.72	0.53	0.53
query37	0.11	0.07	0.07
query38	0.07	0.05	0.05
query39	0.05	0.04	0.03
query40	0.20	0.15	0.15
query41	0.09	0.04	0.04
query42	0.05	0.04	0.04
query43	0.05	0.04	0.04
Total cold run time: 98.27 s
Total hot run time: 29.02 s

@zhaorongsheng
Copy link
Contributor Author

run buildall

@hello-stephen
Copy link
Contributor

BE UT Coverage Report

Increment line coverage 0.00% (0/7) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 52.76% (18055/34221)
Line Coverage 37.99% (163686/430872)
Region Coverage 32.36% (124741/385479)
Branch Coverage 33.73% (54546/161715)

@hello-stephen
Copy link
Contributor

BE Regression && UT Coverage Report

Increment line coverage 0.00% (0/7) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 71.36% (23925/33526)
Line Coverage 57.75% (248714/430673)
Region Coverage 52.85% (206219/390194)
Branch Coverage 54.56% (88652/162488)

@zhaorongsheng
Copy link
Contributor Author

run buildall

@hello-stephen
Copy link
Contributor

BE UT Coverage Report

Increment line coverage 0.00% (0/7) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 52.77% (18065/34236)
Line Coverage 38.00% (163826/431108)
Region Coverage 32.37% (124876/385737)
Branch Coverage 33.74% (54606/161821)

@hello-stephen
Copy link
Contributor

BE Regression && UT Coverage Report

Increment line coverage 0.00% (0/7) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 71.42% (23959/33548)
Line Coverage 57.84% (249324/431043)
Region Coverage 53.03% (207150/390631)
Branch Coverage 54.69% (88984/162712)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Be core during hot/cold cooldown progress

3 participants