-
Notifications
You must be signed in to change notification settings - Fork 11
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
Loading model weights more efficiently #119
Labels
feature
Categorizes issue or PR as related to a new feature.
needs-priority
Indicates a PR lacks a label and requires one.
needs-triage
Indicates an issue or PR lacks a label and requires one.
Milestone
Comments
InftyAI-Agent
added
needs-triage
Indicates an issue or PR lacks a label and requires one.
needs-kind
Indicates a PR lacks a label and requires one.
needs-priority
Indicates a PR lacks a label and requires one.
labels
Sep 2, 2024
/milestone v0.1.0 |
/kind feature |
InftyAI-Agent
added
feature
Categorizes issue or PR as related to a new feature.
and removed
needs-kind
Indicates a PR lacks a label and requires one.
labels
Sep 2, 2024
/assign |
We may implement a simplified p2p network for efficient model distributing. See https://github.com/InftyAI/Manta |
How transformer handles large models: https://huggingface.co/docs/transformers/big_models |
/assign |
/milestone v0.2.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
feature
Categorizes issue or PR as related to a new feature.
needs-priority
Indicates a PR lacks a label and requires one.
needs-triage
Indicates an issue or PR lacks a label and requires one.
What would you like to be added:
Right now we can download model weights from model hub directly, but each time we start/restart a pod, it will downloading the model weights again. Without the loading accelerators like fluid or dragonfly, we should think of a way to tackle this more efficiently, let's focus on three things:
Why is this needed:
Completion requirements:
This enhancement requires the following artifacts:
The artifacts should be linked in subsequent comments.
The text was updated successfully, but these errors were encountered: