Kuiz berkaitan panduan · Sederhana Tahap
Kuiz Model Transformer Hibrid Jamba-Mamba
Semak lapisan hibrid Jamba asal, penghalaan campuran pakar, keadaan berulang, pertumbuhan cache perhatian dan penilaian konteks panjang khusus beban kerja.
soalan 1 daripada 8
Dua jenis lapisan teras yang manakah Jamba selang?
Pratonton setiap soalan8 soalan
Jawapan dan penjelasan muncul semasa anda mengambil kuiz.
- Dua jenis lapisan teras yang manakah Jamba selang?
- Lapisan konvolusi dan penyatuan
- Lapisan RNN dan CNN
- Perhatian pengubah dan lapisan ruang keadaan Mamba
- Lapisan resapan dan perhatian
- Apakah teknik tambahan yang Jamba gunakan untuk meningkatkan kapasiti sambil mengekalkan parameter aktif rendah?
- Campuran pakar (KPM)
- Penyulingan pengetahuan
- Latihan sedar kuantisasi
- Pembelajaran pengukuhan daripada maklum balas manusia
- 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
- Apakah tetingkap konteks yang disokong oleh model Jamba pertama?
- token 4K
- 256K token
- 32K token
- 8 juta token
- 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