[opt](load) Increase the default value of webserver_num_workers#46304
Merged
liaoxin01 merged 1 commit intoapache:masterfrom Jan 8, 2025
Merged
[opt](load) Increase the default value of webserver_num_workers#46304liaoxin01 merged 1 commit intoapache:masterfrom
liaoxin01 merged 1 commit intoapache:masterfrom
Conversation
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Contributor
Author
|
run buildall |
TPC-H: Total hot run time: 32735 ms |
TPC-DS: Total hot run time: 190969 ms |
ClickBench: Total hot run time: 30.79 s |
|
TeamCity be ut coverage result: |
Contributor
|
PR approved by at least one committer and no changes requested. |
Contributor
|
PR approved by anyone and no changes requested. |
github-actions bot
pushed a commit
that referenced
this pull request
Jan 8, 2025
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.
github-actions bot
pushed a commit
that referenced
this pull request
Jan 8, 2025
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
pushed a commit
that referenced
this pull request
Jan 8, 2025
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
To address the issue of insufficient HTTP threads during high-concurrency stream loads causing slow data reception, we increased the number of threads.
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)