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

Abnormal system memory usage while enabling GPU metrics #7144

Open
SkyM31 opened this issue Apr 21, 2024 · 1 comment
Open

Abnormal system memory usage while enabling GPU metrics #7144

SkyM31 opened this issue Apr 21, 2024 · 1 comment

Comments

@SkyM31
Copy link

SkyM31 commented Apr 21, 2024

Description
There is an abnormal system memory usage while enabling GPU metrics.
enable GPU metrics:
command: tritonserver --model-repository=/models
after a long time waiting
185854
Triton Server Started successfully, and it uses about 52GB of system memory!

and disable GPU metrics:
command: tritonserver --model-repository=/models --allow-gpu-metrics=false
triton server immediately started.
image
Now it just uses a little system memory.

I think this problem may be related to the GPU driver version or CUDA version, rather than the Triton version. It seems that there are some problems with the coordination between Triton and the latest version of GPU drivers and CUDA

Triton Information
Triton Version:install from docker images:nvcr.io/nvidia/tritonserver:24.03-py3 (seems 24.02 have same problem, other verison not tested.)

My GPU: NVIDIA GeForce RTX 4060 Ti
Driver Version: 550.54.15
CUDA Version: 12.4

To Reproduce
Just 'docker pull nvcr.io/nvidia/tritonserver:24.03-py3'
And start a container: docker run --gpus all -it --shm-size=256m -p8000:8000 -p8001:8001 -p8002:8002 -v /your/dir/:/models
This problem seems to be unrelated to the type of model you are using, at least not to onnxruntime backend and tensorrt backend.
entry tritonserver --model-repository=/models Press Enter and monitor the memory resource usage

@SkyM31
Copy link
Author

SkyM31 commented Apr 21, 2024

To add, this problem did not occur when using RTX3090, Driver Version: 535.x(may be not this version, last test with RTX3090 was a long time ago)
if you execute the 'nvidia-smi' command inside the container, it will take a long time to read hardware information, even stuck. Instead of immediately obtaining GPU information
image

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

No branches or pull requests

1 participant