引导式测验 · 中等 等级
Jamba 混合变压器-Mamba 模型问答
查看原始 Jamba 混合层、专家混合路由、循环状态、注意力缓存增长和特定于工作负载的长上下文评估。
问题 1 的 8
Jamba 交错哪两种核心层类型?
预览每个问题8 问题
当您参加测验时,就会出现答案和解释。
- Jamba 交错哪两种核心层类型?
- 卷积层和池化层
- RNN 和 CNN 层
- Transformer 注意力和 Mamba 状态空间层
- 扩散层和注意力层
- Jamba 使用什么附加技术来增加容量,同时保持较低的活动参数?
- 混合专家 (MoE)
- 知识蒸馏
- 量化感知训练
- 从人类反馈中强化学习
- 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
- 第一个 Jamba 模型支持什么上下文窗口?
- 4K代币
- 256K 代币
- 32K 代币
- 800 万个代币
- 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