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

[Core] Disk tier best is not the best possible disk #3517

Open
romilbhardwaj opened this issue May 7, 2024 · 0 comments
Open

[Core] Disk tier best is not the best possible disk #3517

romilbhardwaj opened this issue May 7, 2024 · 0 comments

Comments

@romilbhardwaj
Copy link
Collaborator

On AWS, sky launch -c aws --cloud aws --disk-tier best provisions a gp3 EBS with 7000 IOPS and 437MB/s throughput.

On the other hand, the "best" possible EBS (discounting io2) is io1 with 64000 IOPS and 1 GB/s throughput:
image

Similar behavior may exist on other clouds, need to verify.

I understand SkyPilot is using its "high" disk tier as the "best", but that is ~9x fewer IOPS and half the throughput you can get from the "best" EBS. Using the best possible configuration is particularly important for performance of disk-heavy workloads.

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

1 participant