[Efficiency improvement] GGUF conversion - file caching. #286
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.
One line fix - ggufwriter will cache to file instead of living in ram.
It's a bit slower naturally, but I think it's unreasonable to demand - what is it, 24gb ram? I get crashes on 12gb at 54% - to store a full flux model in memory, when it's a one time operation.
As mentioned in #285 , this will allow running conversions even on low resource containers (colab, space presumably).
In terms of disk space, you need <100gb free for the base, temp and converted files mainly; colab supplies that much.