MergeOver: Post-Training Token Merging for Recursive Vision Transformers
MergeOver is a post-training method that integrates Token Merging into recursively weight-shared Vision Transformers to significantly reduce memory usage and latency on edge devices while maintaining high accuracy, all without requiring costly retraining.
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 trying to teach a super-smart robot to recognize cats, dogs, and cars just by looking at pictures. To do this, the robot uses a special kind of brain called a "Vision Transformer." Think of this brain as a team of tiny detectives, where every single pixel in a photo gets its own detective. The more pixels there are, the more detectives you need, and the more they have to talk to each other to figure out what they are seeing. This is great for accuracy, but it's a huge problem for small computers, like the ones in your smartwatch or a Raspberry Pi, because they don't have enough memory or battery power to handle thousands of detectives chatting at once.
To fix this, scientists have tried two main tricks. The first is "recursive weight-sharing," which is like having one super-detective who does the same job over and over again, reusing their notes instead of hiring a new team for every step. This saves space but makes the detective work slower and heavier. The second trick is "token merging," where you realize that some detectives are looking at the same thing, so you just merge them into one big detective to save time. The big question this paper tackles is: What happens if you try to use both tricks at the same time without having to retrain the whole robot from scratch? It's like trying to teach a single detective to merge with their clones while they are already working, without messing up the map they are following.
The authors of this paper, Junseo Kim and his team from the University of Twente, say that trying to mix these two methods is usually a disaster because the rules of the game get broken. They propose a new method called MergeOver to solve this puzzle. Imagine the robot's brain is a multi-story building where the detectives move up floors. Every time they move to a new floor, the building's architecture requires them to stand in a perfect square grid. But merging detectives usually messes up that square grid, leaving empty spots that break the elevator. MergeOver introduces a clever "Unmerge" trick: it temporarily splits the merged detectives back into their original grid positions just long enough to get through the elevator, and then merges them again once they are safe on the next floor. This allows the robot to keep its memory usage low without needing to be retrained.
The team tested this on a famous picture dataset called ImageNet-1K, using different types of computers, from powerful graphics cards to a tiny Raspberry Pi 5. They found that MergeOver works, but the results depend heavily on how many pictures you ask the robot to look at at once (the "batch size"). When the robot looks at just one picture at a time, the extra work of merging and unmerging actually slows things down a bit. However, when the robot looks at 16 pictures at once, the magic happens. On a powerful GPU, this setup reduced the memory needed by 38.4% and actually made the robot 21.7% faster. On the tiny Raspberry Pi, it made the robot 17.6% faster for batches of 16. The best part is that the robot didn't get much dumber; its accuracy only dropped by 1.47 percentage points, which the authors say is a small price to pay for such a big speed boost.
However, the paper is careful to note that this isn't a magic wand that fixes everything instantly. The authors explicitly argue against the idea that you can just slap this on any model and expect it to work perfectly everywhere. They found that for single-picture tasks (batch size 1), the method actually slows things down on powerful computers because the overhead of the "Unmerge" trick isn't worth it for just one image. They also point out that while their method saves a lot of memory and speeds up batch processing, it doesn't necessarily beat all other types of efficient AI models that were designed from the ground up to be fast. The results are measured and real, but they suggest that this is a promising starting point—a "baseline"—for combining these techniques, rather than a final, perfect solution. The authors suggest that future work might need to combine MergeOver with other tricks, like better software optimization, to make it even faster, especially for those single-picture tasks on small devices.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.