Automatically reusing components
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- huggingface, python
- Área
- machine-learning
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Python
- Estrellas
- 34.9k
- Forks
- 7.5k
- Merge medio
- 3 d 16 h
- PR fusionados (30 d)
- 65
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de huggingface/diffusers
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
huggingface/diffusers#15363 ·
Los mantenedores suelen responder en 1 día
-
`ZImageImg2ImgPipeline` / `ZImageInpaintPipeline`: explicit height/width different from the input image raises RuntimeErrorPosiblemente ocupada @chessing234 la tomó hace 1 día. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
huggingface/diffusers#15337 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Multi-vector textual inversion uses only the first vector when the token has uppercase letters (transformers v5)Posiblemente ocupada @sunhouy la tomó hace 2 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
huggingface/diffusers#15313 ·
Los mantenedores suelen responder en 1 día
-
TCDScheduler advances the generator on the final step of a strength-truncated custom schedulePosiblemente ocupada @SIDDARTHAREDDY8 la tomó hace 5 días. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
huggingface/diffusers#15288 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
unload_textual_inversion(token) leaves the extra tokens of a multi-vector embedding behind, so it can't be loaded againPosiblemente ocupada @sohailshk la tomó hace 11 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
huggingface/diffusers#15211 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
Todos los issues de huggingface/diffusers
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
Los mantenedores suelen responder en 1 día
-
Unused loot bag group names left in dreamcraft en_US.langPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. AbiertoStatus: Triage Suggestion
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
GTNewHorizons/GT-New-Horizons-Modpack#27789 ·
Los mantenedores suelen responder en 1 día
-
bug frontend sev-5
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
-
core good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
b4b code health next
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
ESCOMP/CTSM#4330 · 1 comentario ·
Los mantenedores suelen responder en 1 día