-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Conversation
[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 |
@xiaofan-luan E2e jenkins job failed, comment |
@xiaofan-luan ut workflow job failed, comment |
cb00127
to
70441ea
Compare
@xiaofan-luan E2e jenkins job failed, comment |
@xiaofan-luan ut workflow job failed, comment |
70441ea
to
0b2a943
Compare
@xiaofan-luan E2e jenkins job failed, comment |
pkg/util/conc/future.go
Outdated
@@ -71,6 +71,11 @@ func (future *Future[T]) Err() error { | |||
return future.err | |||
} | |||
|
|||
func (future *Future[T]) SetErr(err error) { |
There was a problem hiding this comment.
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", |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
0b2a943
to
639714d
Compare
@xiaofan-luan ut workflow job failed, comment |
@xiaofan-luan E2e jenkins job failed, comment |
639714d
to
e7ebb12
Compare
@xiaofan-luan E2e jenkins job failed, comment |
e7ebb12
to
6e45af9
Compare
Codecov Report
Additional details and impacted files@@ 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
|
@xiaofan-luan E2e jenkins job failed, comment |
@xiaofan-luan ut workflow job failed, comment |
6e45af9
to
02fec89
Compare
@xiaofan-luan E2e jenkins job failed, comment |
/run-cpu-e2e |
@xiaofan-luan E2e jenkins job failed, comment |
/run-cpu-e2e |
@xiaofan-luan E2e jenkins job failed, comment |
02fec89
to
ea59f23
Compare
@xiaofan-luan E2e jenkins job failed, comment |
ea59f23
to
b81db02
Compare
@xiaofan-luan E2e jenkins job failed, comment |
b81db02
to
9cef2cc
Compare
@xiaofan-luan E2e jenkins job failed, comment |
/run-cpu-e2e |
@xiaofan-luan E2e jenkins job failed, comment |
/run-cpu-e2e |
@xiaofan-luan E2e jenkins job failed, comment |
9cef2cc
to
b4fae5f
Compare
@xiaofan-luan E2e jenkins job failed, comment |
b4fae5f
to
9001b50
Compare
@xiaofan-luan E2e jenkins job failed, comment |
/run-cpu-e2e |
@xiaofan-luan E2e jenkins job failed, comment |
Signed-off-by: xiaofan-luan <[email protected]>
9001b50
to
0156bc0
Compare
@xiaofan-luan E2e jenkins job failed, comment |
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:
Required Title Structure:
Where Example:
Please review and update your PR to comply with these guidelines. |
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. |
fix #27456