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

‌‌‌‌‌After using the Huggingface integration solution, will a model occupy twice the disk space? #3270

Open
yetone opened this issue May 15, 2024 · 4 comments

Comments

@yetone
Copy link

yetone commented May 15, 2024

‌‌‌‌‌‌I'm very happy to see the integration solution of Huggingface. I'm curious whether this will cause Hugging Face's models to occupy double disk space (dragonfly cache directory + huggingface cache directory)?

https://d7y.io/docs/next/operations/integrations/hugging-face/

@gaius-qi
Copy link
Member

Yes, it is possible to optimize Dfdaemon's GC configuration and reduce the cache size .
Refer to https://d7y.io/docs/next/reference/configuration/dfdaemon.

image

@yetone
Copy link
Author

yetone commented May 15, 2024

‌‌‌Thanks, I'll look into it!

@yetone
Copy link
Author

yetone commented May 15, 2024

@gaius-qi Will there be any adverse effects if I completely use dragonfly's cache and disable hugging face's own cache? Specifically, our goal is to have different containers utilize the same model cache.

@gaius-qi
Copy link
Member

@gaius-qi Will there be any adverse effects if I completely use dragonfly's cache and disable hugging face's own cache? Specifically, our goal is to have different containers utilize the same model cache.

If model has cached in d7y, huggingface sdk will download by http proxy. Slower but reduce the space.

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