Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Improve Activation Scoring of Puzzletron

Aperta
  • Qualcosa non va?
#1,820 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

@Separius ci sta già lavorando.

Dal 25/6/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

feature request

Feature Request: Improve Activation Scoring of Puzzletron

Description

The current activation scoring implementation in Puzzletron has architectural limitations that hinder scalability, model support, and training efficiency. This request addresses three critical gaps: the lack of multi-hook execution, limited architectural support compared to Minitron, and missing distributed parallelization capabilities.

1. Multi-Hook Activation Scoring Runs

Currently, the system executes separate, suboptimal scoring rounds for individual hooks (e.g., one for FFN channel importance and another for query heads). This approach becomes entirely unmanageable with complex architectures like nemotron3-super, which require concurrent hooks for attention, Mamba, shared experts, individual expert channels, expert removal, and latent MoE. The scoring pipeline must be refactored to handle unified, multi-hook activation scoring within a single run to reduce redundant overhead.

2. Expanded Architecture Support

Puzzletron is currently limited to FFN channel scoring. In contrast, Minitron already includes mature support for Mamba layers and baseline capabilities for Mixture of Experts (MoE) layers. These existing layer-scoring features need to be ported directly from Minitron to Puzzletron to achieve feature parity and enable broader model profiling.

3. Comprehensive Distributed Parallelization

As model sizes scale and initial checkpoints utilize increasingly massive sequence lengths, Puzzletron requires robust distributed training infrastructure. We need to add full support for Expert Parallelism (EP), Tensor Parallelism (TP), Context Parallelism (CP), and Fully Sharded Data Parallel (FSDP). This should be achieved by introducing comprehensive AutoModel support that functions seamlessly under both configurations:

  • force_hf = True
  • force_hf = False
Business & Engineering Impact

Resolving these bottlenecks will significantly reduce the computational overhead of profiling next-generation architectures, unblock pruning workflows for MoE/Mamba models, and ensure our optimization tools scale to enterprise-level foundation checkpoints.

Lingua principale
Python
Stelle
5.2k
Fork
736
Merge medio
3g 14h
PR unite (30g)
160

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di NVIDIA/Model-Optimizer

Tutte le issue di NVIDIA/Model-Optimizer

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.