Repository navigation
Daytona: derive GPU types from the pricing feed - #286
Open
mislavivanda wants to merge 1 commit into
Open
mislavivanda wants to merge 1 commit into
mislavivanda wants to merge 1 commit into
Conversation
Every GPU type in Daytona's public pricing feed is orderable, so the feed alone now decides which GPUs are offered instead of a hardcoded GPU_MAP. Daytona type identifiers are resolved against gpuhunt's known accelerators by dropping separators (RTX-PRO-6000 -> RTXPRO6000), which also provides vendor and GPU memory. This adds the now-available B200 and L40S, and future Daytona GPUs that gpuhunt already knows appear without code changes. - Memory shape: 50 GB per GPU for GPUs with <= 32 GB GPU memory, 100 GB otherwise (unchanged results for all current types). - Unknown accelerators are still skipped with a warning. - Integrity tests check offers against the live feed and fail if the feed contains a GPU type gpuhunt does not know. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Mislav Ivanda <mislavivanda454@gmail.com>
Contributor
|
@mislavivanda, the PR looks good. A real E2E test uncovered a separate issue affecting the existing dstack integration, which I've reported in dstackai/dstack#4494. When starting a Daytona run, the sandbox starts, but SSH setup fails with: dstack requests a ten-year expiry, which previously worked. The current 24-hour limit prevents runs from completing provisioning, independently of this PR. Could Daytona restore support for long SSH-token expiries? Requesting 24 hours would fix startup, but reliable access for longer runs would then require credential renewal in dstack. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
Makes the Daytona provider derive its GPU types from Daytona's public pricing feed (
https://billing.app.daytona.io/gpu-pricing) instead of the hardcodedGPU_MAP.Every GPU type in that feed is orderable, so the feed alone can decide what is offered. This adds the now-available B200 and L40S (both creatable since Daytona 0.225.0 / 0.231.0), and future Daytona GPUs that gpuhunt already knows appear without a code change.
How
find_accelerators) by dropping separators:RTX-PRO-6000→RTXPRO6000,RTX-5090→RTX5090. Vendor and GPU memory come from the matchedAcceleratorInfo.provider_data["gpu_type"]keeps the original Daytona identifier whenever it differs from the gpuhunt name, so dstack's Daytona backend keeps passing the rightgpuTypeto the create API.Testing
76 passed.GPU_MAP. They validate offers against the live feed and add a check that every feed GPU type resolves to a known accelerator, so a brand-new chip surfaces as a CI failure rather than being silently dropped:11 passedagainst the live feed.python -m gpuhunt daytona: 9 GPU types × 8 counts × on-demand/spot + 2 CPU offers = 146 offers.🤖 Generated with Claude Code