← Latest papers
🤖 machine learning

Information Routing across Batch Boundaries: Memory--Batch Tradeoffs in Lipschitz Bandits

This paper characterizes the minimax expected pseudo-regret in stochastic Lipschitz bandits under simultaneous constraints on memory width (WW) and batch depth (BB), revealing a fundamental information-routing tradeoff where these parameters are non-interchangeable and jointly determine a new regret frontier of Td+2d+3(1+(B1)W)1d(d+3)T^{\frac{d+2}{d+3}} (1+(B-1)W)^{-\frac1{d(d+3)}}.

Original authors: Zicheng Lyu, Zengfeng Huang

Published 2026-08-11
📖 7 min read🧠 Deep dive

Original authors: Zicheng Lyu, Zengfeng Huang

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

The Great Balancing Act: Learning with a Tiny Brain and a Slow Voice

Imagine you are a detective trying to solve a massive mystery, but you have two very strict rules. First, you can only carry a tiny notebook with you; if you write down too much, you have to throw something out to make room for new clues. Second, you can't shout your theories out loud immediately. Instead, you have to write a plan, go out and gather evidence based on that plan, come back, and then you are allowed to rewrite your plan for the next round. You can't change your mind while you are out in the field.

This is the world of "bandit problems," a famous puzzle in the science of decision-making. In this field, an agent (like a robot or a computer program) has to choose between different options to find the best one, like a gambler picking the best slot machine or a doctor picking the best medicine. The catch is that the agent doesn't know which option is best at the start; it has to learn by trying them out and seeing what happens. Usually, scientists assume the agent has a super-brain that remembers everything and can change its mind instantly after every single try. But in the real world, computers have limited memory, and sometimes we can't update our strategies instantly—we have to wait for a "batch" of results to come in.

This paper asks a fascinating question: If you are forced to use a tiny notebook (limited memory) and you can only update your plan a few times (limited batches), how badly will you mess up? Is it better to have a slightly bigger notebook and update your plan often, or a huge notebook and update rarely? The authors of this paper, Zicheng Lyu and Zengfeng Huang, dive deep into this trade-off to find the exact mathematical limit of how well you can learn under these constraints.

The Detective's Dilemma: Memory vs. Updates

The authors set up a game where a learner is trying to find the highest peak in a foggy, mountainous landscape. The landscape is smooth (mathematically, it's "Lipschitz"), meaning if you are close to a high point, you are probably near a high point. The learner can take steps (pulls) to measure the height, but they have two strict limits:

  1. Memory Width (WW): After every step, the learner can only keep a tiny amount of information (a few bits) in their "live" notebook. They can't store the whole history of the trip.
  2. Batch Depth (BB): The learner must group their steps into "batches." They pick a plan, take a bunch of steps, and only after all those steps are done can they look at the results and change their plan for the next batch. They can't change the plan while they are in the middle of the batch.

The big question is: How do these two limits work together? Can a super-wide memory make up for having very few chances to update? Or does having many updates make up for a tiny memory?

The Big Discovery: You Cannot Bypass the System

The paper's main finding is a bit of a bummer for anyone hoping to find a magic shortcut: Memory and updates are not interchangeable. You cannot just swap one for the other.

The authors prove that to do a good job, you need both enough memory to hold the important clues and enough updates to act on them. They found a new mathematical formula that describes the "regret" (how much worse you do compared to a perfect expert). This formula has three parts:

  1. The difficulty of the landscape itself (how many mountains there are).
  2. The penalty for not being able to update your plan often enough.
  3. The new penalty: A specific cost that comes from trying to squeeze too much information through a narrow memory pipe with too few update opportunities.

Think of it like trying to send a long letter through a post office that only accepts small envelopes, and you can only mail a letter once a week.

  • If you have a huge memory (a giant warehouse of notes) but can only mail a letter once (one batch), you are stuck. You can't send the crucial details of the new clues you found because you can't change your plan until the week is over.
  • If you can mail a letter every day (many batches) but your envelope is tiny (low memory), you have to throw away most of your notes after every step. You might remember to go north, but you forget why you went north, so you can't refine your path.

The authors show that the worst-case performance is determined by the weakest link in this chain. If your memory is too small to hold the "map" of where the good spots are, having a million updates won't help. If you can't update your plan often enough, having a library of memory won't help either.

The "Information Routing" Bottleneck

The paper introduces a cool concept called Information Routing. Imagine the landscape is divided into many small regions. To find the best spot, the learner has to make a decision for each region: "Is this region worth exploring further?"

The problem is that the learner has to carry these decisions across the "batch boundaries" (the times when they are allowed to update).

  • The Memory (WW) limits how many decisions they can carry in their pocket at one time.
  • The Batches (BB) limit how many times they can stop, look at their pocket, and decide to change their route.

The authors prove that if you try to compress all your decisions into a tiny summary to save space, you lose too much detail. If you try to keep every detail, you run out of space. The optimal strategy is a delicate dance: keep just enough information to know which regions are "safe" to explore, and throw away the rest of the raw data immediately.

They found that to get close to the performance of a perfect, unlimited learner, you need a specific amount of memory (roughly the logarithm of the total time) and a specific number of updates (roughly the logarithm of the logarithm of the total time). If you have less than that, your performance drops significantly.

What This Means for the Future

The paper doesn't just say "it's hard." It gives a precise recipe for how hard it is. They proved that if you have enough memory (about log(T)\log(T) bits, where TT is the total number of steps) and enough batches, you can almost match the performance of a learner with infinite memory and instant updates. But if you fall short on either, you hit a wall.

They also showed that being "smart" about when you update (using adaptive boundaries) doesn't actually help you beat the worst-case scenario. Whether you update at fixed times or try to be clever about it, the fundamental limits of your memory and update count still apply.

In short, this paper tells us that in the world of learning with limited resources, you can't have your cake and eat it too. You need a balance. You need a notebook big enough to hold the map, and you need enough chances to redraw that map. If you try to cut corners on either, the math says you will pay the price. It's a fundamental rule of the universe of learning: State width and update depth are partners, not substitutes.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →