Questionário vinculado ao guia · Médio Nível
Questionário de modelos Jamba Hybrid Transformer-Mamba
Revise as camadas híbridas originais do Jamba, o roteamento misto de especialistas, o estado recorrente, o crescimento do cache de atenção e a avaliação de longo contexto específica da carga de trabalho.
Pergunta 1 de 8
Quais são os dois tipos de camadas principais que o Jamba intercala?
Visualize cada pergunta8 perguntas
As respostas e explicações aparecem conforme você responde ao teste.
- Quais são os dois tipos de camadas principais que o Jamba intercala?
- Camadas convolucionais e de pooling
- Camadas RNN e CNN
- Atenção do transformador e camadas de espaço de estado do Mamba
- Camadas de difusão e atenção
- Que técnica adicional o Jamba usa para aumentar a capacidade enquanto mantém os parâmetros ativos baixos?
- Mistura de especialistas (MoE)
- Destilação de conhecimento
- Treinamento com reconhecimento de quantização
- Aprendizagem por reforço com feedback humano
- 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
- Qual janela de contexto o primeiro modelo Jamba suportava?
- Tokens 4K
- 256 mil tokens
- 32 mil tokens
- 8 milhões de fichas
- 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