Unloading vision model of VLMs for Exllamav3 backend#393
Merged
kingbri1 merged 1 commit intotheroyallab:mainfrom Nov 20, 2025
Merged
Unloading vision model of VLMs for Exllamav3 backend#393kingbri1 merged 1 commit intotheroyallab:mainfrom
kingbri1 merged 1 commit intotheroyallab:mainfrom
Conversation
This change ensures that when unloading vlm their vision part is also unloaded.
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
2 participants
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.
This is a small PR that ensures that vision model of a VLM is unloaded and doesn't stay in VRAM indefinitely.
I've used a few exl3 VLMs and noticed that after unloading them a noticeable amount of VRAM was kept reserved by TabbyAPI.
Exl3 backend unload function was missing code to unload the vision part.