---
title: "STaR-KV Slashes UI-TARS GPU Memory by 40% Without Retraining"
subtitle: "STaR-KV cuts peak GPU memory by 40% for GUI agents by rethinking how KV cache tokens are scored and pruned at inference time"
url: "https://alphasignal.ai/news/star-kv-slashes-ui-tars-gpu-memory-by-40-without-retraining"
author: "AlphaSignal Newsroom"
author_url: "https://alphasignal.ai/editorial-team"
company: "AlphaSignal"
company_url: "https://alphasignal.ai/company/alphasignal"
published: "2026-06-01T00:00:00.000Z"
updated: "2026-06-09T10:07:48.463Z"
type: "Paper"
topics:
  - "Infra"
  - "Image"
subtopics:
  - "Inference Optimization"
  - "Vision Language"
upvotes: 1219
source_url: "https://arxiv.org/abs/2606.01790"
comments: 0
truncated: true
---

# STaR-KV Slashes UI-TARS GPU Memory by 40% Without Retraining

> STaR-KV cuts peak GPU memory by 40% for GUI agents by rethinking how KV cache tokens are scored and pruned at inference time

Running a GUI agent for more than a few steps is quietly becoming a hardware problem. A single task typically ingests tens of high-resolution screenshots as historical context, causing the KV cache to grow linearly with the number of interaction steps. The KV cache -- the memory structure that stores intermediate attention states so the model does not have to reprocess every past token -- is the culprit. Since GUI tasks typically involve high-resolution screenshots and extended interaction trajectories, the size of the KV cache grows linearly with sequence length, leading to severe GPU memory saturation and inference latency.

The numbers are stark. According to the paper, UI-TARS-1.5-7B -- ByteDance's state-of-the-art GUI agent -- consumes 76 GB of GPU memory on just five screenshots, nearly filling an 80 GB A100 or H100\. Scale that to a real task with dozens of steps and you have a model that simply cannot run on any single accelerator. Running inference on UI-TARS-1.5-7B with bfloat16 and flash attention on a 5-screenshot example for a single step can take over 15 seconds on an H200 on average. Memory and latency are both walls.

## Why existing compression methods fall short

Large Vision-Language Models have emerged as powerful engines for autonomous GUI agents, yet their deployment is severely constrained by the substantial memory footprint and latency of the Key-Value cache during long-horizon interactions. The research community has responded with a wave of KV compression techniques -- SnapKV, H2O, PyramidKV, GUIKV -- but these were largely designed for text-heavy LLMs or general vision tasks. They suffer from suboptimal performance in GUI scenarios due to a fundamental misalignment: unlike general visual tasks where attention sparsity varies across layers, GUI attention patterns exhibit uniform high-sparsity across all transformer layers.

_Preview only. Full text requires an AlphaSignal Pro account._

## Sources

- [STaR-KV: Spatio-Temporal Adaptive Re-weighting for KV Cache Compression in GUI Vision-Language Models](https://arxiv.org/abs/2606.01790)
- [STaR-KV HTML paper (full text)](https://arxiv.org/html/2606.01790v1)
- [GUI-KV: Efficient GUI Agents via KV Cache with Spatio-Temporal Awareness](https://arxiv.org/abs/2510.00536)
- [Efficient Long-Horizon GUI Agents via Training-Free KV Cache Compression (ST-Lite)](https://arxiv.org/abs/2603.00188)
- [ByteDance-Seed/UI-TARS-1.5-7B on Hugging Face](https://huggingface.co/ByteDance-Seed/UI-TARS-1.5-7B)