Kvíz spojený s průvodcem · Střední úroveň
Prompt Compression Quiz
Reduce prompt tokens while measuring compressor overhead, end-to-end latency, task quality, and the risk of losing critical context.
Otázka 1 z 8
What does prompt compression try to achieve?
Náhled každé otázky8 otázky
Odpovědi a vysvětlení se zobrazují, jak budete v kvízu.
- What does prompt compression try to achieve?
- Guarantee that every model answer improves
- Reduce input tokens while retaining information needed for the task
- Replace evaluation with a shorter prompt
- Remove all system instructions
- What did LLMLingua research investigate?
- Guaranteed lossless compression for every task
- A model that only answers in JSON
- Removing the need for retrieved context
- Prompt compression methods intended to reduce inference cost and latency while preserving useful information
- Why can compression harm an answer?
- It may remove an exception, constraint, or rare detail needed for the task
- It always increases context length
- It prevents models from reading text
- It changes only the output format
- When can compression increase end-to-end latency?
- Whenever prompts are compressed
- Only when the answer is correct
- When compressor overhead is greater than the time saved in model processing
- When a prompt contains no text
- What should be measured when evaluating a compression method?
- Only the compression ratio
- Token reduction, compressor time, cost, latency, and task quality
- Only model output length
- Only GPU memory
- Which prompt content should a compressor preserve carefully?
- Task goals, constraints, exceptions, definitions, and needed evidence
- Repeated filler at all costs
- Only the first sentence
- Every punctuation mark regardless of meaning
- What may happen if a prompt is already short or cached?
- The compressor always makes the request free
- The model stops using its cache
- The prompt becomes longer by definition
- Compression overhead may exceed the remaining savings
- How should a team verify a compressed prompt?
- Assume fewer tokens means equal quality
- Test only the example used to create it
- Compare it with the original on representative held-out examples
- Skip version tracking