Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Jan 8, 2025

Cherry-picked from #46304

@yiguolei
Copy link
Contributor

yiguolei commented Jan 8, 2025

run buildall

@doris-robot
Copy link

TeamCity be ut coverage result:
Function Coverage: 36.41% (9564/26265)
Line Coverage: 27.98% (79003/282375)
Region Coverage: 26.65% (40506/152011)
Branch Coverage: 23.41% (20532/87716)
Coverage Report: http://coverage.selectdb-in.cc/coverage/fffdbf1e88fa6fc3132029b1641e2fbd3b69a91e_fffdbf1e88fa6fc3132029b1641e2fbd3b69a91e/report/index.html

1. In high-concurrency stream load scenarios, there aren't enough
webserver threads available.
2. During stream load, after data reception and while waiting for
execution, the synchronous wait occupies HTTP threads.

To address the issue of insufficient HTTP threads during
high-concurrency stream loads causing slow data reception, we increased
the number of threads.
@yiguolei yiguolei force-pushed the auto-pick-46304-branch-2.1 branch from fffdbf1 to d57122d Compare January 8, 2025 14:38
@yiguolei
Copy link
Contributor

yiguolei commented Jan 8, 2025

run buildall

@doris-robot
Copy link

TeamCity be ut coverage result:
Function Coverage: 36.42% (9565/26265)
Line Coverage: 27.98% (78998/282372)
Region Coverage: 26.64% (40500/152005)
Branch Coverage: 23.40% (20525/87714)
Coverage Report: http://coverage.selectdb-in.cc/coverage/d57122d6ec26d4bbbbf66dfaeeded8743600f3c6_d57122d6ec26d4bbbbf66dfaeeded8743600f3c6/report/index.html

@liaoxin01 liaoxin01 closed this Jan 21, 2025
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.

4 participants