Repository navigation
Automatically use CPU for API-only evaluations - #67
Merged
Merged
Conversation
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.
API-only panels now automatically use CPU compute, enforced server-side for both submissions and spec previews. Panels containing Hugging Face models use GPU in the form. CPU routing applies to regular LAISR-funded accounts as well as admins and personal-key runs, and admin CPU limits are checked after compute selection.
The form hides GPU controls and stock checks for API-only panels and labels the shared option “LAISR Lab compute”. Credit enforcement remains disabled by default; existing admin limits still apply.
Validation: 100 backend tests passed (5 skipped), including CPU selection, mixed panels, preview consistency, and CPU-limit enforcement. TypeScript and production frontend build passed.