Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The previous IOPS was selected to keep the
HIGH
disk tier's performance for all clouds similar to each other. Should we instead create a newDiskTier.ULTRA
for the max possible IOPS?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see. How about we change DiskTier.BEST to the actual best possible disk tier?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right now,
BEST
is the best DiskTier amongLOW
,MEDIUM
,HIGH
provided by SkyPilot right now (some clouds may not haveHIGH
tier, soBEST
will map toMEDIUM
in that case).I am fine with changing the semantics of
BEST
to the actual best disk available on a specific cloud. This is related to #3585 and #3517.