Automatically reusing components
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Facilidade para iniciantes
- 35/100
- Tipo de issue
- Funcionalidade
- Clareza
- Claramente especificada
- Status de atividade
- Ativa
- Stack de tecnologia
- huggingface, python
- Domínio
- machine-learning
Direção de pesquisa
Read the ComponentsManager guide and the Pika H3 Flex example linked in the issue to understand how components are currently shared. The proposal is to discuss opt-in reuse based on checkpoint weight hashes; this issue explicitly asks for feedback and use cases rather than a code change. Share a concrete concern, alternative, or experience with manual component reuse.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Diffusers pipelines often share components: the same text encoder or VAE across model families, a finetune reusing its base model's components, a LoRA-based model reusing the base transformer entirely. Loading each of them twice wastes time, and worse, it keeps two copies of the same model in memory. So we want to reuse the same components as much as possible.
What we have today
In Modular Diffusers, ComponentsManager manages components across pipelines. Load one pipeline through it, and a second pipeline can pick up what it needs from the manager instead of loading its own copy:
pika.update_components(transformer=manager.get_one(name="transformer", collection="minimax-h3"))
See the ComponentsManager guide and the Pika H3 Flex example, where a second pipeline is assembled from a loaded MiniMax-H3.
The reuse itself is still manual: you decide which components are shared and pass them over. What the manager gives you is bookkeeping so you can keep track of it. Each component is listed once with the pipelines that use it (when you register under a collection), offloading works across all of them, and the manager warns when two components were loaded from the same repo and subfolder. That warning is as far as duplicate detection goes today, and it comes after the second copy is already loaded.
The Hub now dedups on disk
With huggingface_hub>=1.32.0, identical Xet-backed files share one cached payload across repositories, shard by shard. Download the same text encoder from two repos and it lands on disk once. We could take advantage of that and go one step further: dedup the models we load into memory too.
Proposal
An opt-in setting on the manager. When a pipeline is about to load a component, the manager checks whether the same weights are already loaded, using the same idea the Hub uses to dedup: a content hash of the weights, stored with the checkpoint and compared before loading. If there is a match, the pipeline reuses the loaded component instead of loading again. No download, no second copy.
How to contribute
This issue carries the new idea-contribution-welcome label. For issues with this label we are not looking for a PR. We are looking for discussion: feedback on the proposal, alternatives, use cases we have not thought of, problems you ran into with the current manual way. We will write the PR ourselves, and anyone whose feedback shaped it will be added as a co-author.
Posted by Claude on behalf of @yiyixuxu. The text was drafted together and approved by yiyixuxu.
- Linguagem predominante
- Python
- Estrelas
- 34.9k
- Forks
- 7.5k
- Merge médio
- 3d 16h
- PRs com merge (30d)
- 65
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de huggingface/diffusers
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 84/100
huggingface/diffusers#15363 ·
Mantenedores costumam responder em até 1 dia
-
`ZImageImg2ImgPipeline` / `ZImageInpaintPipeline`: explicit height/width different from the input image raises RuntimeErrorTalvez já em andamento @chessing234 assumiu há 1 dia. Abertabug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
huggingface/diffusers#15337 · 2 comentários ·
Mantenedores costumam responder em até 1 dia
-
Multi-vector textual inversion uses only the first vector when the token has uppercase letters (transformers v5)Talvez já em andamento @sunhouy assumiu há 2 dias. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 75/100
huggingface/diffusers#15313 ·
Mantenedores costumam responder em até 1 dia
-
TCDScheduler advances the generator on the final step of a strength-truncated custom scheduleTalvez já em andamento @SIDDARTHAREDDY8 assumiu há 5 dias. Abertabug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 74/100
huggingface/diffusers#15288 · 2 comentários ·
Mantenedores costumam responder em até 1 dia
-
unload_textual_inversion(token) leaves the extra tokens of a multi-vector embedding behind, so it can't be loaded againTalvez já em andamento @sohailshk assumiu há 11 dias. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
huggingface/diffusers#15211 · 3 comentários ·
Mantenedores costumam responder em até 1 dia
Todas as issues de huggingface/diffusers
Issues semelhantes
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 73/100
Mantenedores costumam responder em até 1 dia
-
Unused loot bag group names left in dreamcraft en_US.langTalvez já em andamento Um pull request vinculado a esta issue está aberto ou já foi mesclado. AbertaStatus: Triage Suggestion
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 90/100
GTNewHorizons/GT-New-Horizons-Modpack#27789 ·
Mantenedores costumam responder em até 1 dia
-
bug frontend sev-5
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 83/100
-
core good first issue
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 65/100
-
b4b code health next
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
ESCOMP/CTSM#4330 · 1 comentário ·
Mantenedores costumam responder em até 1 dia