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]: The GPU memory usage is much larger than the actual vector data #32333

Open
1 task done
longyxiang opened this issue Apr 16, 2024 · 4 comments
Open
1 task done
Assignees
Labels
kind/bug Issues or changes related a bug stale indicates no udpates for 30 days triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@longyxiang
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version:2.3.12
- Deployment mode(standalone or cluster):standalone 
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):Go
- OS(Ubuntu or CentOS): CentOS
- CPU/Memory: 
- GPU: A10
- Others:

Current Behavior

The GPU memory usage is much larger than the actual vector data,512-dimensional vector data

微信图片_20240416194851
微信图片_20240416194858

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

@longyxiang longyxiang 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 Apr 16, 2024
@xiaofan-luan
Copy link
Contributor

/assign @Presburger @liliu-z

@liliu-z
Copy link
Member

liliu-z commented Apr 17, 2024

Talked offline. This memory is occupied by GPU mem pool. We are working on adding a mem pool usage metrics to help monitor it.

@liliu-z
Copy link
Member

liliu-z commented Apr 17, 2024

Another issue to track this : zilliztech/knowhere#507

@yanliang567 yanliang567 added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 17, 2024
@yanliang567 yanliang567 removed their assignment Apr 17, 2024
Copy link

stale bot commented May 18, 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 May 18, 2024
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/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

5 participants