Resetting-induced instability in queues fed by a search process in an interval

This paper investigates a queuing system with limited servers fed by a search process in a bounded domain subject to stochastic resetting, identifying a critical threshold resetting rate that determines whether resetting expands or shrinks the parameter regions for steady-state convergence and demonstrating that this threshold grows exponentially with the number of servers.

Original authors: José Giral-Barajas, Paul C. Bressloff

Published 2026-05-06
📖 5 min read🧠 Deep dive

Original authors: José Giral-Barajas, Paul C. Bressloff

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 a busy warehouse (the target) where workers are constantly trying to deliver packages (the resources). These packages are brought by a delivery driver (the searcher) who drives randomly around a city block (the interval) looking for the warehouse door.

Once the driver finds the door, they drop off a package, drive back to their starting point to reload, and go out searching again. Meanwhile, inside the warehouse, a team of workers (the servers) is busy unpacking and processing these packages.

The big question this paper asks is: Will the warehouse eventually fill up with an endless pile of packages, or will the workers keep up with the deliveries and reach a steady, manageable level?

The answer depends on two main things:

  1. How fast the driver finds the door.
  2. How many workers are inside.

The "Reset" Twist

In this story, the driver has a special trick: Stochastic Resetting. This means that every now and then, randomly, the driver gets a sudden urge to give up on their current path and instantly teleport back to their starting point to try again.

Usually, in physics, we think "resetting" is a good thing. If you are looking for something in a huge, empty field, stopping and restarting from the beginning can actually help you find it faster. It's like realizing you're walking in circles and deciding to just go back to the start.

However, this paper discovers a surprising twist: In a busy warehouse system, resetting can sometimes make things worse.

The Two Scenarios

1. The "Too Long" City Block (Long Interval)

Imagine the city block is very long.

  • Without Resetting: If the driver starts far away, it takes them a long time to find the warehouse. They deliver packages slowly. The workers inside have plenty of time to process them, so the pile of packages stays manageable.
  • With Resetting: If we add the "teleport back" rule, the driver might find the warehouse faster on average. They deliver packages more frequently.
  • The Problem: If the driver delivers packages too fast, the workers inside can't keep up. The pile of packages starts to grow uncontrollably, eventually overflowing the warehouse.
  • The Finding: For long city blocks, adding resetting can actually shrink the "safe zone." It turns a situation where the warehouse was stable into one where it overflows.

2. The "Short" City Block (Short Interval)

Now, imagine the city block is very short.

  • Without Resetting: The driver is already close to the warehouse. They find it quickly. If they start too close, they might deliver packages so fast that the workers can't keep up, causing an overflow.
  • With Resetting: If the driver starts very close, resetting forces them to go back to the start, which actually slows down their delivery rate.
  • The Benefit: This "slow down" can be a good thing! It gives the workers inside a chance to catch up. In this specific case, resetting expands the "safe zone," allowing the system to stay stable even if the driver starts in a spot that would have caused a disaster before.

The "Tipping Point"

The authors found a specific "tipping point" (a threshold) that determines which of these two effects happens:

  • If the city block is shorter than this point, resetting helps stabilize the warehouse.
  • If the city block is longer than this point, resetting destabilizes it and causes overflow.

The "More Workers" Rule

The paper also looked at what happens if you hire more workers (increase the number of servers).

  • You might think hiring more workers makes the system more robust.
  • However, the paper found that as you add more workers, the "resetting rate" needed to actually help the system grows exponentially.
  • The Analogy: Imagine you have a small team of 5 workers. A little bit of "resetting" (slowing the driver down) might help them. But if you have a massive team of 1,000 workers, you would need an enormous amount of resetting to make a difference. In fact, for large teams, it becomes incredibly difficult for resetting to help; it's much more likely to just mess things up and cause an overflow.

Summary

This paper is a warning to system managers: Just because a strategy (like resetting) makes a search process faster, doesn't mean it makes the whole system more stable.

  • If you have a small team and a short search area, resetting might help you stay organized.
  • If you have a large team or a long search area, forcing the searcher to reset often can actually cause the system to collapse under the weight of too many arrivals.

The authors provide mathematical formulas to tell you exactly where that line is drawn, so you know when to use resetting and when to avoid it.

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 →