Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(performance)[scanner] Isolate local and remote queries using different scanner… #11006

Merged
merged 8 commits into from
Jul 29, 2022

Conversation

luwei16
Copy link
Contributor

@luwei16 luwei16 commented Jul 19, 2022

Proposed changes

Issue Number: close #xxx

Problem Summary:

Scanner thread pool shared by remote data and local data query. The high latency of remote data query will occupy the thread pool worker thread and affect the performance of local data query.

Therefore, a remote scanner thread pool for remote data query is added to avoid the impact on local query.

Checklist(Required)

  1. Does it affect the original behavior: (Yes/No/I Don't know)
  2. Has unit tests been added: (Yes/No/No Need)
  3. Has document been added or modified: (Yes/No/No Need)
  4. Does it need to update dependencies: (Yes/No)
  5. Are there any changes that cannot be rolled back: (Yes/No)

Further comments

If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...

@luwei16 luwei16 changed the title (cold_on_s3) Isolate local and remote queries using different scanner… (improvement)[scanner] Isolate local and remote queries using different scanner… Jul 19, 2022
@luwei16 luwei16 changed the title (improvement)[scanner] Isolate local and remote queries using different scanner… (performance)[scanner] Isolate local and remote queries using different scanner… Jul 19, 2022
be/src/common/config.h Outdated Show resolved Hide resolved
// number of s3 scanner thread pool size
CONF_Int32(doris_s3_scanner_thread_pool_thread_num, "48");
// number of s3 scanner thread pool queue size
CONF_Int32(doris_s3_scanner_thread_pool_queue_size, "102400");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

102400 is too big,

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

changed to 10240

be/src/exec/olap_scan_node.cpp Outdated Show resolved Hide resolved
@@ -200,6 +201,7 @@ class ExecEnv {

// TODO(cmy): find a better way to unify these 2 pools.
PriorityThreadPool* _scan_thread_pool = nullptr;
PriorityThreadPool* _s3_scan_thread_pool = nullptr;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

_s3_scan_thread_pool need to be _remote_scan_thread_pool

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

pengxiangyu
pengxiangyu previously approved these changes Jul 26, 2022
Copy link
Contributor

@pengxiangyu pengxiangyu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@github-actions
Copy link
Contributor

PR approved by anyone and no changes requested.

Copy link

@kpfly kpfly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@dataroaring dataroaring left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dataroaring dataroaring merged commit d6f937c into apache:master Jul 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants