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] Parallel GPU Memory Capacity unbalance #1563

Closed
2 tasks done
ruifengma opened this issue May 9, 2024 · 3 comments
Closed
2 tasks done

[Bug] Parallel GPU Memory Capacity unbalance #1563

ruifengma opened this issue May 9, 2024 · 3 comments
Assignees

Comments

@ruifengma
Copy link

Checklist

  • 1. I have searched related issues but cannot get the expected help.
  • 2. The bug has not been fixed in the latest version.

Describe the bug

I'm trying to deploy InternVL-Chat 1.5. When I use the official repo(InternVL-Chat 1.5)controller-worker-gradio web server architecture to deploy the model, it took around 32GB/46GB,33GB/46GB on two A40 GPUs. But When I use lmdeploy, it took 43G/46G and 32G/46G for the same two A40 GPUs.

Reproduction

CUDA_VISIBLE_DEVICES=0,1 lmdeploy serve api_server /home/models/InternVL-Chat-V1-5/ --model-name InternVL-Chat-V1-5 --server-port 23333 --tp2

Environment

OS:CentOS 7
Python=3.10
CUDA=12.1
Torch=2.2.1 (via pip)

Error traceback

No response

@ruifengma
Copy link
Author

This is actually reduce the capability for high concurrency because for the 43G/46G GPU, it can easily OOM for more than 2 requests

@irexyc
Copy link
Collaborator

irexyc commented May 9, 2024

Currently, the vision model are not loaded balanced, we are working on this and should be fixed in the next release.

For now you can change this value to 1 and see if it could prevent OOM. Using a smaller value of cache-max-entry-count will also reduce the memory usage.

@ruifengma
Copy link
Author

Currently, the vision model are not loaded balanced, we are working on this and should be fixed in the next release.

For now you can change this value to 1 and see if it could prevent OOM. Using a smaller value of cache-max-entry-count will also reduce the memory usage.

Thanks @irexyc for the advices, I tried to lower the value cache-max-entry-count from default 0.8 to 0.6 and the corresponding GPU memory capacity is lower to 40G/46G and 29G/46G. Anyway, thanks for the excellent work and advice, when do we plan to release the the next version? Looking forward to that : )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants