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

Reduce go routine and thread numbers #27457

Closed
wants to merge 1 commit into from

Conversation

xiaofan-luan
Copy link
Collaborator

fix #27456

@sre-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: xiaofan-luan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@sre-ci-robot sre-ci-robot added approved size/L Denotes a PR that changes 100-499 lines. labels Sep 30, 2023
@mergify mergify bot added the dco-passed DCO check passed. label Sep 30, 2023
@mergify
Copy link
Contributor

mergify bot commented Sep 30, 2023

@xiaofan-luan E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

@mergify
Copy link
Contributor

mergify bot commented Sep 30, 2023

@xiaofan-luan ut workflow job failed, comment rerun ut can trigger the job again.

@sre-ci-robot sre-ci-robot added size/XL Denotes a PR that changes 500-999 lines. and removed size/L Denotes a PR that changes 100-499 lines. labels Sep 30, 2023
@mergify
Copy link
Contributor

mergify bot commented Sep 30, 2023

@xiaofan-luan E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

@mergify
Copy link
Contributor

mergify bot commented Sep 30, 2023

@xiaofan-luan ut workflow job failed, comment rerun ut can trigger the job again.

@mergify
Copy link
Contributor

mergify bot commented Sep 30, 2023

@xiaofan-luan E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

pkg/util/conc/future.go Outdated Show resolved Hide resolved
@@ -71,6 +71,11 @@ func (future *Future[T]) Err() error {
return future.err
}

func (future *Future[T]) SetErr(err error) {
Copy link
Member

Choose a reason for hiding this comment

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

This method may be abused to set error of future multiple times, but the channel can't be closed twice

@@ -1777,7 +1776,7 @@ Max read concurrency must greater than or equal to 1, and less than or equal to
p.MaxGroupNQ = ParamItem{
Key: "queryNode.grouping.maxNQ",
Version: "2.0.0",
DefaultValue: "1000",
DefaultValue: "100",
Copy link
Member

Choose a reason for hiding this comment

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

@liliu-z does this fit Knowhere?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

this is to avoid merge cost latency up.

Copy link
Member

@liliu-z liliu-z Oct 1, 2023

Choose a reason for hiding this comment

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

@yah01 big NQ will introduce big latency in nowadays search arch. Let’s reduce it for now until we can find some other solutions

@mergify
Copy link
Contributor

mergify bot commented Oct 1, 2023

@xiaofan-luan ut workflow job failed, comment rerun ut can trigger the job again.

@mergify
Copy link
Contributor

mergify bot commented Oct 1, 2023

@xiaofan-luan E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

@mergify
Copy link
Contributor

mergify bot commented Oct 1, 2023

@xiaofan-luan E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

@codecov
Copy link

codecov bot commented Oct 1, 2023

Codecov Report

Merging #27457 (9001b50) into master (0c69f48) will decrease coverage by 0.31%.
Report is 333 commits behind head on master.
The diff coverage is 86.44%.

❗ Current head 9001b50 differs from pull request most recent head 0156bc0. Consider uploading reports for the commit 0156bc0 to get more accurate results

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master   #27457      +/-   ##
==========================================
- Coverage   81.78%   81.47%   -0.31%     
==========================================
  Files         833      804      -29     
  Lines      117802   114194    -3608     
==========================================
- Hits        96340    93040    -3300     
+ Misses      18265    18024     -241     
+ Partials     3197     3130      -67     
Files Coverage Δ
internal/querynodev2/segments/collection.go 97.58% <100.00%> (ø)
internal/querynodev2/segments/plan.go 70.17% <100.00%> (-4.39%) ⬇️
internal/querynodev2/segments/search.go 89.09% <100.00%> (+4.47%) ⬆️
internal/querynodev2/tasks/search_task.go 42.17% <ø> (ø)
pkg/metrics/metrics.go 100.00% <ø> (ø)
pkg/metrics/querynode_metrics.go 100.00% <ø> (ø)
pkg/util/conc/future.go 100.00% <100.00%> (ø)
pkg/util/indexparams/disk_index_params.go 87.19% <ø> (ø)
pkg/util/paramtable/component_param.go 98.08% <33.33%> (-0.05%) ⬇️
internal/querynodev2/segments/retrieve.go 94.44% <94.23%> (+9.75%) ⬆️
... and 1 more

... and 230 files with indirect coverage changes

@mergify
Copy link
Contributor

mergify bot commented Oct 1, 2023

@xiaofan-luan E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

@mergify
Copy link
Contributor

mergify bot commented Oct 1, 2023

@xiaofan-luan ut workflow job failed, comment rerun ut can trigger the job again.

@mergify
Copy link
Contributor

mergify bot commented Oct 2, 2023

@xiaofan-luan E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

@xiaofan-luan
Copy link
Collaborator Author

/run-cpu-e2e

@mergify
Copy link
Contributor

mergify bot commented Oct 2, 2023

@xiaofan-luan E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

@xiaofan-luan
Copy link
Collaborator Author

/run-cpu-e2e

@mergify
Copy link
Contributor

mergify bot commented Oct 2, 2023

@xiaofan-luan E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

@mergify
Copy link
Contributor

mergify bot commented Oct 2, 2023

@xiaofan-luan E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

@mergify
Copy link
Contributor

mergify bot commented Oct 8, 2023

@xiaofan-luan E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

@mergify
Copy link
Contributor

mergify bot commented Oct 8, 2023

@xiaofan-luan E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

@xiaofan-luan
Copy link
Collaborator Author

/run-cpu-e2e

@mergify
Copy link
Contributor

mergify bot commented Oct 8, 2023

@xiaofan-luan E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

@xiaofan-luan
Copy link
Collaborator Author

/run-cpu-e2e

@mergify
Copy link
Contributor

mergify bot commented Oct 8, 2023

@xiaofan-luan E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

@mergify
Copy link
Contributor

mergify bot commented Oct 8, 2023

@xiaofan-luan E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

@mergify
Copy link
Contributor

mergify bot commented Oct 9, 2023

@xiaofan-luan E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

@xiaofan-luan
Copy link
Collaborator Author

/run-cpu-e2e

@mergify
Copy link
Contributor

mergify bot commented Oct 9, 2023

@xiaofan-luan E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

Copy link
Contributor

mergify bot commented Nov 1, 2023

@xiaofan-luan E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

Copy link
Contributor

mergify bot commented Nov 16, 2023

@xiaofan-luan

Invalid PR Title Format Detected

Your PR submission does not adhere to our required standards. To ensure clarity and consistency, please meet the following criteria:

  1. Title Format: The PR title must begin with one of these prefixes:
  • feat: for introducing a new feature.
  • enhance: for improvements to existing functionality.
  • fix: for bug fixes.
  1. Description Requirement: The PR must include a non-empty description, detailing the changes and their impact.

Required Title Structure:

[Type]: [Description of the PR]

Where Type is one of feat, enhance, or fix.

Example:

feat: Enhance search functionality within the user interface

Please review and update your PR to comply with these guidelines.

Copy link

stale bot commented Dec 16, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.

@stale stale bot added the stale indicates no udpates for 30 days label Dec 16, 2023
@stale stale bot closed this Dec 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved dco-passed DCO check passed. do-not-merge/invalid-pr-format size/XL Denotes a PR that changes 500-999 lines. stale indicates no udpates for 30 days
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Enhancement]: Reduce goroutine and control concurrency
4 participants