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

[Bug]: CPU usage is high with huge collection numbers same as #26157 #31514

Closed
1 task done
Seven2Nine opened this issue Mar 22, 2024 · 4 comments
Closed
1 task done
Assignees
Labels
kind/bug Issues or changes related a bug stale indicates no udpates for 30 days triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@Seven2Nine
Copy link

Seven2Nine commented Mar 22, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: 2.3.5
- Deployment mode(standalone or cluster): standalone 
- MQ type(rocksmq, pulsar or kafka): rocksmq
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): Ubuntu 
- CPU/Memory: 4vCPUs 16G--aws t3.xlarge
- GPU: 
- Others:

Current Behavior

1500 collections
each collection 100 entities.

CPU usage > 70% when idle.
image

Expected Behavior

https://github.com/milvus-io/milvus/issues/26157

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

@Seven2Nine Seven2Nine added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 22, 2024
@yanliang567
Copy link
Contributor

please retry on latest milvus v2.3.12, which improved a lot for the scenarios of multi collections @Seven2Nine
/assign @Seven2Nine
/unassign

@yanliang567 yanliang567 added triage/needs-information Indicates an issue needs more information in order to work on it. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 22, 2024
@xiaofan-luan
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: 2.3.5
- Deployment mode(standalone or cluster): standalone 
- MQ type(rocksmq, pulsar or kafka): rocksmq
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): Ubuntu 
- CPU/Memory: 4vCPUs 16G--aws t3.xlarge
- GPU: 
- Others:

Current Behavior

1500 collections each collection 100 entities.

CPU usage > 70% when idle. image

Expected Behavior

https://github.com/milvus-io/milvus/issues/26157

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

Did you have pprof for datacoord?
how many segments/partititons are there in each collection on avg?

Copy link

stale bot commented Apr 22, 2024

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 Apr 22, 2024
@stale stale bot closed this as completed May 5, 2024
@xiaofan-luan
Copy link
Contributor

@yanliang567
is this still a problem in 2.4?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues or changes related a bug stale indicates no udpates for 30 days triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

3 participants