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

[Feature]: Support the Capacity Blocks for ML feature for AWS #1155

Open
Tracked by #1782 ...
peterschmidt85 opened this issue Apr 22, 2024 · 9 comments · May be fixed by #1977
Open
Tracked by #1782 ...

[Feature]: Support the Capacity Blocks for ML feature for AWS #1155

peterschmidt85 opened this issue Apr 22, 2024 · 9 comments · May be fixed by #1977
Labels
feature good first issue Good for newcomers

Comments

@peterschmidt85
Copy link
Contributor

peterschmidt85 commented Apr 22, 2024

Problem

With AWS, Capacity Blocks for ML is the main way to access H100 today.

Solution

No response

Workaround

No response

Would you like to help us implement this feature by sending a PR?

Yes

@r4victor
Copy link
Collaborator

@peterschmidt85, please describe what's meant by the support for Capacity Blocks. Do you suggest dstack provides an interface to purchase reserved instances or do you suggest dstack should be able to launch instances in capacity blocks purchased by users?

@r4victor
Copy link
Collaborator

Also note that testing EC2 Capacity Blocks for ML can be costly. The minimum reservation price is p4d.24xlarge for 1 day =. $14.75 * 24 = $354.

@peterschmidt85
Copy link
Contributor Author

@peterschmidt85, please describe what's meant by the support for Capacity Blocks. Do you suggest dstack provides an interface to purchase reserved instances or do you suggest dstack should be able to launch instances in capacity blocks purchased by users?

@r4victor I think, we only need to add a way to specify the existing reservation ID. I believe this can be a field in YAML/Profile.

@peterschmidt85
Copy link
Contributor Author

This issue is stale because it has been open for 30 days with no activity.

@peterschmidt85
Copy link
Contributor Author

This issue is stale because it has been open for 30 days with no activity.

@peterschmidt85
Copy link
Contributor Author

This issue was closed because it has been inactive for 14 days since being marked as stale. Please reopen the issue if it is still relevant.

@peterschmidt85 peterschmidt85 closed this as not planned Won't fix, can't repro, duplicate, stale Jul 14, 2024
@jvstme jvstme reopened this Jul 24, 2024
@peterschmidt85 peterschmidt85 added the good first issue Good for newcomers label Aug 22, 2024
Copy link

This issue is stale because it has been open for 30 days with no activity.

@solovyevt
Copy link

solovyevt commented Oct 8, 2024

Working on this.

@peterschmidt85 One question: this issue covers capacity blocks only, ignoring generic capacity reservations, correct?

@peterschmidt85
Copy link
Contributor Author

Working on this.

@peterschmidt85 One question: this issue covers capacity blocks only, ignoring generic capacity reservations, correct?

@solovyevt This particular issue I suppose is about capacity blocks only - because as far as I understand they are commonly used for ML (https://aws.amazon.com/blogs/aws/announcing-amazon-ec2-capacity-blocks-for-ml-to-reserve-gpu-capacity-for-your-machine-learning-workloads/)

@solovyevt solovyevt linked a pull request Nov 9, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants