Skip to content

Conversation

@Kosinkadink
Copy link
Collaborator

Before:

loaded partially 20034.674988555907 20024.842895507812 0
loaded completely 20126.8 7909.737449645996 True

After:

loaded partially; 20034.67 MB usable, 20024.84 MB loaded, 18943.05 MB offloaded, lowvram patches: 0
loaded completely; 1199.53 MB usable, 242.03 MB loaded, full load: True

@Kosinkadink Kosinkadink changed the title Improve 'load completely' and 'load partially' log statements Improve 'loaded completely' and 'loaded partially' log statements Oct 29, 2025
@comfyanonymous comfyanonymous merged commit 998bf60 into master Oct 29, 2025
12 checks passed
@comfyanonymous comfyanonymous deleted the improve-load-logs branch October 29, 2025 23:37
@isaac-mcfadyen
Copy link

Is it possible this PR might have messed up some of the numbers?

I just got a log output of:

loaded completely; 95367431640625005117571072.00 MB usable, 14776.55 MB loaded, full load: True

I definitely do not have that much VRAM 😅

@Kosinkadink
Copy link
Collaborator Author

Kosinkadink commented Oct 30, 2025

No, this PR did not mess with any numbers. What you're seeing is how --high-vram startup argument works - it makes the model management system pretend it has "infinite" VRAM, AKA a super big float.

@isaac-mcfadyen
Copy link

Ah, makes sense - thanks for the clarification!

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.

4 participants