Skip to content

feat: make negative max_vram control the amount of spare vram#1503

Open
wbruna wants to merge 1 commit into
leejet:masterfrom
wbruna:sd_max_vram_neg
Open

feat: make negative max_vram control the amount of spare vram#1503
wbruna wants to merge 1 commit into
leejet:masterfrom
wbruna:sd_max_vram_neg

Conversation

@wbruna
Copy link
Copy Markdown
Contributor

@wbruna wbruna commented May 16, 2026

Summary

Repurpose the -1 sentinel value to mean "spare this amount of free VRAM".

1 GiB can be a lot in certain circumstances: for instance, a small card, or a dedicated one which doesn't need to keep that much free VRAM available. The user could choose a positive value specific for their case, but that would miss the ability to calculate a good value from the available VRAM.

I've kept the documentation and help texts as-is for now to avoid a big diff, but I'll adapt them if this feature is considered useful.

Checklist

@leejet
Copy link
Copy Markdown
Owner

leejet commented May 17, 2026

Please update the document.

-1 still means 1 GiB, but e.g. -0.2 would spare only 0.2 GiB.
@wbruna wbruna force-pushed the sd_max_vram_neg branch from 51e160d to 9b9d109 Compare May 17, 2026 20:08
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.

2 participants