- Rating
- 2
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper studies visual token pruning when attention-based rankings change across language-model layers. DIPrune combines a token's current text-to-vision attention rank with its rank improvement over adjacent layers, aiming to retain both currently salient and emerging task-relevant tokens. The method performs a single pruning step inside the language model and uses a separate attention calculation compatible with efficient attention kernels. Experiments on LLaVA and Qwen-VL variants report strong accuracy retention at reduced token counts, with additional evaluations of pruning position, score components, latency, and broader visual tasks.
Critical strengths
Substantial supplementary evaluation. The paper includes Qwen3 dense/MoE models, generative and grounding tasks, component ablations, and cross-architecture timing. This is broader than the main LLaVA tables alone suggest.
Critical weaknesses
- The main token-budget comparison is not fully auditable. DIPrune's “64 tokens” is the count after one-shot pruning at L10; earlier layers still process the full sequence. In contrast, PyramidDrop's original Table 2 labels its budgets as average tokens. The manuscript does not provide the evaluated PDrop/SparseVLM layer schedules or a common FLOPs table. The layer-matched VisionZip/HoloV controls are helpful, but do not resolve the whole main-table comparison.
- The claimed suppression mechanism is stronger than the empirical evidence. Figures 2–3 establish persistence and changes in attention rank, but identify later-important tokens using later attention itself. A token can remain highly attended because it is useful, so persistence alone does not establish redundancy or suppression of answer-critical evidence. Appendix B.2 supports the score's usefulness, but does not independently test this causal explanation. The paper should distinguish the observed ranking pattern from the mechanism claimed to produce it.
Questions for authors
- Please give the actual per-layer visual-token counts and total prefill FLOPs for every Table 1 method at the “64 tokens” setting. Were PDrop/SparseVLM budgets converted from layer averages to post-pruning counts, or reimplemented with another schedule?
- Do existing experiments independently test the claimed suppression of answer-relevant tokens? Otherwise, can this be presented as an observed ranking pattern motivating the heuristic, rather than an established causal mechanism?