Skip to content

recommend(): 0.5 GB tolerance so nameplate min_vram tiers are reachable - #59

Merged
TroyHernandez merged 1 commit into
mainfrom
fix/vram-tier-tolerance
Aug 12, 2026
Merged

recommend(): 0.5 GB tolerance so nameplate min_vram tiers are reachable#59
TroyHernandez merged 1 commit into
mainfrom
fix/vram-tier-tolerance

Conversation

@TroyHernandez

Copy link
Copy Markdown
Contributor

Fixes #56.

The tier table's min_vram values are nameplate card sizes (8, 12, 16...), but recommend() compares them against detected FREE VRAM, and no card reports its nameplate as free: a real 8 GB card shows ~7.5-7.9 GB. So every nameplate-valued tier (the flux-family 8 GB nf4 tiers, SDXL's 12 GB full-GPU tier, flux2's 16 GB bf16 tier) was unreachable on exactly the card it targets, silently dropping to the CPU tier.

One-line fix, option 2 from the issue: a 0.5 GB tolerance in the single comparison, keeping the tier table's readable nameplate numbers. The CPU tier (min_vram = 0) is unaffected. Tests pin the boundary: vram_gb = 7.6 selects the flux2 8 GB GPU tier, 7.4 drops to CPU; all 92 existing recommend tests unchanged.

Fixes #56. min_vram thresholds are nameplate card sizes but vram_gb is
free VRAM; an 8 GB card reports ~7.5-7.9 free, so the flux-family 8 GB
tiers (and every other nameplate-valued threshold) silently dropped to
the CPU tier on exactly the cards they target.
@TroyHernandez
TroyHernandez merged commit 20ec54a into main Aug 12, 2026
2 checks passed
@TroyHernandez
TroyHernandez deleted the fix/vram-tier-tolerance branch August 12, 2026 03:07
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

Successfully merging this pull request may close these issues.

recommend(): min_vram tiers equal to a card's nameplate capacity are unreachable via auto-detect

1 participant