Merged
Conversation
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
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.
Add multi-GPU and memory-efficient model loading to HuggingfaceSubject
Changes
HuggingfaceSubjectnow loads models withdevice_map='auto', automatically distributing layers across all available GPUs. Single-GPU and MPS (Apple Silicon) behavior is unchanged.low_cpu_mem_usage=Truetofrom_pretrained, reducing peak CPU RAM during checkpoint loading from ~3x to ~1x model size.Why
Models over ~6B parameters in float32 exceed a single 24 GB GPU. Previously, all weights were loaded onto GPU 0 regardless of how many GPUs were available, causing OOM kills on multi-GPU instances (e.g. g5.12xlarge). This fix allows 7-13B models to run in fp32 on multi-GPU instances without any changes to individual model plugins.
Impact