Bean Network Tester

Limit download and upload speed

Throttle one application to a set number of kilobytes per second and it gets no more than that. The two directions are separate, so you can give it a fast download and a hopeless upload - which is exactly what most home and mobile connections look like.

In the window

  1. Set Process to your application.
  2. Fill Download, Upload or both, in KB/s. Leave a field at 0 to leave that direction alone.
  3. Press START.
BeanNetworkTester.exe --down 128 --up 32 --target myapp.exe --duration 120

What the numbers mean

KB/sRoughlyWhat it is
656 kbit/sA dial-up modem. The "56k modem" profile.
1281 Mbit/sIn-flight WiFi, a busy hotel, a bad mobile signal.
10248 Mbit/sA modest home line. Enough for one video stream.
12800100 Mbit/sA normal fixed connection today.

Kilobytes, not kilobits - so multiply by eight to compare with what an internet provider advertises. Throttling both directions at once is what makes a connection feel like a bad hotspot rather than merely a slow download.

The queue matters as much as the limit

A speed limit needs somewhere to put the packets that do not fit yet. That is the Buffer setting, in milliseconds, and it behaves like the queue at a checkout:

The "Congested home link (bufferbloat)" profile is exactly this: a limit with a long queue. Try the same speed with a short queue and a long one, and watch how differently the app behaves.

One thing to expect

With a limit running, the counter for dropped packets can stay at zero. That is not a bug: a limit first makes packets wait, and it only drops them when the queue is genuinely full. Give it a small buffer and the drops appear.

Next

Ready to break your own network on purpose?

Download for Windows