Guide-yakabatana mibvunzo · Pakati Nhanho
KV Cache Optimization Quiz
Checks KV-cache growth, paged allocation, grouped query sharing, prefix reuse conditions, quantization, and memory scaling with context and concurrency.
Mubvunzo 1 ye 8
Ko KV cache inochengeterei uye nei?
Tarisa mubvunzo wese8 mibvunzo
Mhinduro uye tsananguro zvinoonekwa paunenge uchitora bvunzo.
- Ko KV cache inochengeterei uye nei?
- Kare akaverengerwa makiyi ekutarisisa uye kukosha kuti asadzokororwe nhanho imwe neimwe
- Iyo modhi yekudzidziswa data yekudzidzirazve
- Mapassword emushandisi ekutendesa
- Mhedzisiro inobuda chete
- Sei iyo KV cache ichigona kuve dambudziko rekurangarira?
- Iyo inoshatisa iyo GPU zvachose
- Inokura nehurefu hwekutevedzana, saizi yebatch, uye mitsetse, dzimwe nguva ichipfuura uremu hwemuenzaniso
- Inongoshanda pamashoko mapfupi pane mazwi gumi
- Inodzokorora sisitimu yekushandisa
- Ndeipi inoshanda-system pfungwa inokwereta PagedAttention?
- Disk defragmentation zvishandiso
- Antivirus scanning
- Virtual-memory paging ine yakagadziriswa-saizi mabhuroko
- Screen resolution kuyera
- Ko Grouped-Query uye Multi-Query Attention inoderedza sei KV cache size?
- Nekudzima nzira yekutarisisa
- Nekuchengetedza cache semifananidzo
- Nekudzidziswa pane data shoma
- Nekurega misoro mizhinji yemibvunzo igovane makiyi mashoma / kukosha misoro
- Ndeipi imwe bhenefiti yekugovera prefix muKV cache?
- Zvikumbiro zvine kukurumidza kukurumidza kumwechete zvinogona kushandisa zvakare mabhuroko akafanana
- Iyo encrypts iyo modhi
- Inoderedza chikumbiro chese zvakaenzana
- Inobvisa kudiwa kwekutariswa
- Compared with storing the same KV entries in 16-bit, what does 8-bit storage do to raw cache-value bytes?
- It doubles the raw bytes
- It roughly halves the raw bytes, before metadata and other runtime memory
- It removes the key and value tensors entirely
- It guarantees twice the inference speed
- With full-context attention, no prefix sharing, and a fixed model and cache dtype, what happens if sequence length and batch size both double?
- It stays constant because model weights are fixed
- It roughly doubles
- Raw KV storage grows to roughly four times its previous size
- It becomes one quarter as large
- What must generally match for two requests to reuse the same cached prefix blocks?
- Only the user account name
- The requests must have different model weights
- The prompts must have the same character count but different tokens
- Their tokenized prefix and relevant model/cache configuration must be compatible