Not All Visual Tokens Are Equally Safe to Remove:Consequence-Sensitive Visual Token Compression
This paper introduces a consequence-sensitive visual token compression method for vision-language models that dynamically allocates computational resources based on the potential cost of errors, significantly reducing high-stakes mistakes and overall cost-weighted error rates compared to traditional content-driven or uniform allocation strategies.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are the head chef at a busy restaurant, but you have a strict rule: you can only use a fixed amount of ingredients for every single dish you cook, no matter what it is. Usually, chefs try to make the "average" meal taste as good as possible by spreading those ingredients evenly. But what if one dish is a simple side of fries, while another is a life-saving medicine for a patient? If you mess up the fries, it's annoying. If you mess up the medicine, it's a disaster. Most computer programs that look at pictures and answer questions (called Vision-Language Models) act like that old-school chef. They try to save computing power by ignoring "boring" parts of an image, assuming that every mistake they make costs the same amount of energy. But in the real world, a mistake isn't just a mistake; it has a price tag. This paper asks a simple, revolutionary question: What if we stopped trying to make the average meal perfect, and instead focused our limited ingredients on the dishes where a mistake would be the most expensive?
The researchers behind this study, led by Jingbo Wen and Liang He, propose a new way to handle these computer models called "consequence-sensitive visual token compression." To understand their trick, think of an image not as a single picture, but as a mosaic made of thousands of tiny tiles called "tokens." When a computer looks at a photo, it processes all these tiles. To save time and money, current methods try to throw away the tiles that seem least important, like the blue sky in a photo of a car. They do this by looking at the picture itself to decide what to keep. The authors argue this is like judging a book by its cover; sometimes the "boring" background tiles are actually crucial for the specific question being asked.
Instead of just looking at the picture, the authors suggest looking at the question or the task first. They realized that some questions are "high-stakes" (like "What is the total on this invoice?") and some are "low-stakes" (like "What color is the background?"). Their method works in two steps. First, they run a "calibration" phase offline, where they test the model to see exactly how many tiles (tokens) it needs to get high-stakes questions right versus low-stakes ones. Then, when a real user asks a question, the system checks the "consequence" of getting it wrong. If the question is high-stakes, the system allocates a huge budget of tiles to that image, ensuring the computer sees every detail. If the question is low-stakes, it gets a much smaller budget, saving resources for the important stuff.
The team tested this on a tricky setup where high-stakes and low-stakes questions were asked about the exact same images. This was crucial because it proved that the improvement didn't come from the pictures being different, but purely from how the computer decided to spend its energy. They found that by shifting the budget, they could cut the number of expensive, high-stakes errors by more than half (dropping from 0.300 to 0.133) without using any more total computing power than before. In fact, because they spent less time on the easy questions, the whole system actually ran about 21% faster.
The paper also discovered a "tipping point." When the cost of making a mistake is the same for every question, the best strategy is still to treat everyone equally. But as soon as the cost of a mistake starts to vary (for example, if a wrong answer on a medical report is 5 times worse than a wrong answer on a weather report), the system should start shifting its resources heavily toward the dangerous questions. The researchers showed this works across different types of documents, charts, and even different computer models. They concluded that we shouldn't just measure how "accurate" a model is on average; we should measure how well it prevents the specific, costly mistakes that matter most in the real world.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.