Benchmarks · Long context & retrieval
InfiniteBench
also: ∞Bench
Whether a model can process, retrieve from and reason over inputs longer than 100,000 tokens — a range existing long-context benchmarks at the time mostly stopped well short of.
Tsinghua University (OpenBMB)Released 21 February 2024
InfiniteBench was built to fill a gap that opened as context windows raced past what most existing tests measured: in early 2024, when it was released, public long-context benchmarks mostly topped out around 10,000 tokens, while frontier models were beginning to advertise context windows in the hundreds of thousands. Researchers associated with Tsinghua University’s OpenBMB project built 12 tasks — spanning simple key and passage retrieval, English and Chinese comprehension, code debugging and execution, and mathematics — with average example lengths above 100,000 tokens, and deliberately included tasks that could not be solved by retrieving just a few relevant passages.
Results at launch split sharply by task type. On the simplest retrieval tasks, passkey and number lookup, both GPT-4 and the open-weight Yi-34B-200K scored a perfect 100%, showing that basic long-range retrieval was already close to solved for capable models even at these lengths. On harder tasks that required using information rather than just finding it — such as locating and combining specific numbers scattered through the document in the “Math.Find” task — scores dropped sharply and separated models clearly, with GPT-4 at 60% against Yi-34B-200K’s 25.71%.
That split became InfiniteBench’s lasting contribution: it showed early that “can a model retrieve a fact from very far away” and “can a model reason over a very long input” were different capabilities that saturated at different rates, a distinction that later long-context benchmarks such as RULER and LongBench v2 built on more systematically.
The set
12 tasks across five categories: pure retrieval (passkey, number and key-value lookup), English understanding (summarisation, QA, multiple choice, dialogue), Chinese question answering, code (debugging and execution simulation), and mathematics (calculation and number-finding), with average example lengths above 100,000 tokens and some tasks designed so that retrieving a handful of passages is not enough to answer correctly.
Example
A real 'kv_retrieval' item from the dataset: the context is a JSON object opening with thousands of UUID key-value pairs such as 798c2306-5ad1-42a9-a8de-f2a118b33744: 5e6b7b90-710d-4953-9b18-3e96b2cadbf2, and the model is prompted 'Key: "798c2306-5ad1-42a9-a8de-f2a118b33744" The value associated with the specified key is:' (Answer: 5e6b7b90-710d-4953-9b18-3e96b2cadbf2).huggingface.co
Where it stands
Simple retrieval tasks were close to solved by GPT-4 and Yi-34B-200K even at launch; the harder aggregation, code and maths tasks showed much larger gaps between models and left more room to move.