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

Slow CLIP Feature Extraction on RTX A5000 GPU #104

Open
yashika-git opened this issue Sep 5, 2023 · 7 comments
Open

Slow CLIP Feature Extraction on RTX A5000 GPU #104

yashika-git opened this issue Sep 5, 2023 · 7 comments
Labels
need more info Waiting for more information

Comments

@yashika-git
Copy link

Hello,

Thank you for creating this repository; it has been incredibly helpful.
I'm currently extracting CLIP features, and I've noticed that the extraction is much slower on an RTX A5000 GPU compared to Google Colab's free tier. Additionally, GPU utilization on the A5000 is quite low, while CPU usage is high. I'm using the torch_zoo environment.
Could you please suggest why this might be happening?

Thank you!

@JIA-BIN-CHANG
Copy link

Same issue here, mine GPU is RTX A6000

@v-iashin
Copy link
Owner

hi, sorry for being late with a response.

interesting. i couldn't reproduce it on my A4000 with CLIP features.

however, I noticed something similar when I used it on pwc (with pwc environment)

@v-iashin v-iashin added bug Something isn't working need more info Waiting for more information and removed bug Something isn't working labels Jan 20, 2024
@v-iashin
Copy link
Owner

v-iashin commented Jan 20, 2024

PWC is deprecated from this lib in #112 , the original issue could be a problem. however, I can't replicate it

@v-iashin
Copy link
Owner

if anyone faces the same issue, could you try specifying a higher batch_size (see https://v-iashin.github.io/video_features/models/clip/)?

@yashika-git
Copy link
Author

@v-iashin, Most probably I had tried a higher batch size while extracting CLIP features on an A5000 machine. As far as I remember, the issue still persisted.

@v-iashin
Copy link
Owner

ok, thanks a lot for getting back. i am keeping this open then

@hitcbw
Copy link

hitcbw commented Jun 17, 2024

I suppose that the performance bottleneck comes from the I/O. The gpu utilization is too low.

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

No branches or pull requests

4 participants