Quiz lié à un guide · Moyen Niveau
Quiz sur les modèles Jamba Hybrid Transformer-Mamba
Passez en revue les couches hybrides Jamba d'origine, le routage mixte d'experts, l'état récurrent, la croissance du cache d'attention et l'évaluation de contexte long spécifique à la charge de travail.
Question 1 de 8
Quels sont les deux types de couches principales que Jamba entrelace ?
Prévisualisez chaque question8 des questions
Les réponses et les explications apparaissent au fur et à mesure que vous répondez au quiz.
- Quels sont les deux types de couches principales que Jamba entrelace ?
- Couches convolutives et de pooling
- Couches RNN et CNN
- Attention du transformateur et couches d'espace d'état Mamba
- Couches de diffusion et d’attention
- Quelle technique supplémentaire Jamba utilise-t-il pour augmenter la capacité tout en maintenant les paramètres actifs à un niveau bas ?
- Mélange d'experts (MoE)
- Distillation des connaissances
- Formation prenant en compte la quantification
- Apprentissage par renforcement à partir des commentaires humains
- How does a Mamba layer's recurrent representation differ from an attention layer's KV cache?
- It removes every model parameter from memory
- It skips all tokens beyond the first one
- It stores an independent full copy of every earlier attention matrix
- It maintains a fixed-size recurrent state instead of retaining a growing set of past keys and values
- Quelle fenêtre contextuelle le premier modèle Jamba prenait-il en charge ?
- Jetons 4K
- 256 000 jetons
- 32 000 jetons
- 8 millions de jetons
- What is a reason to retain attention components alongside state-space layers in a Jamba-style hybrid?
- To combine different access and representation mechanisms while evaluating their quality-efficiency tradeoff
- To guarantee perfect retrieval of every token on every task
- To make all attention computation independent of sequence length
- To eliminate the need for any model evaluation
- How should Jamba's reported long-context memory benefit be evaluated for deployment?
- Assume every 256K request fits any single GPU
- Count only the recurrent state while ignoring weights and attention cache
- Measure the actual model, precision, batch size, context, and hardware configuration
- Treat every hybrid model as having zero sequence-state cost
- Does original Jamba's use of many Mamba layers make the whole model's sequence memory constant as input length grows?
- Yes; every hybrid attention cache has a fixed one-token size
- No; its retained attention layers still store a growing KV cache
- Yes; model weights disappear once the sequence becomes long
- Only the tokenizer's file size changes
- Why are total MoE parameters and active parameters per token different quantities in Jamba?
- Every stored expert is necessarily deleted when inactive
- A token must run all experts regardless of routing
- The model's supported context directly sets its vocabulary size
- Routing can activate only a subset of stored experts for each token