-
Notifications
You must be signed in to change notification settings - Fork 4
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
Feature Request: support GPU selection based on additional resources (e.g. available VRAM) #148
Comments
might get solved by #141 ? |
this is already supported by provider codebase as well as clients |
Adding the missing
|
@troian Unfortunately, this didn't seem to work:
provider attributes:
then we tried removing the
didn't help 😕 |
…AMD support in addition to NVIDIA models (#249) * feat(bid-script/gpu): support model.vram for pricing calculation fixes akash-network/support#148 * feat(bid-script/gpu): support AMD in addition to NVIDIA models
Goal
Provider have 40gb a100's on the network and they are adding 80gb a100's too.
They're the same model but different VRAM.
They are wondering whether to just label everything a100-80gb or so?
Implementation (PoC)
CONFIG
Label the worker node with
40Gi
&80Gi
a100
's as follows:provider.yaml
):provider.yaml
fora100.40Gi
SDL test for requesting
a100-40
GPU:TEST1
Provider thinks there is
insufficient capacity
:Somehow the akash-provider reads
vendor/nvidia/model/a100/40Gi
(notice,ram
isn't there) based on the following client SDL and attempts to evaluate40Gi
as something it doesn't have (value:true
??) which is interesting:The text was updated successfully, but these errors were encountered: