Back to Home
4.94/5(1,390 verified benchmarks)
Throughput Telemetry

dstat Testing — Real-Time Bandwidth & Packet Rate Benchmarking

1 Second
Graph Resolution
Real-time bandwidth & Mpps telemetry
3+ Tbps
Bandwidth Ceiling
Stress test 10G, 40G, and 100G interfaces
500M+ Mpps
Packet Rates
High-density packet generation
Rx / Tx / CPU
Metric Capture
Complete system telemetry

Monitor network interface throughput, socket utilization, and system resource consumption in real time during high-capacity stress tests.

Boota vs Basic Ping / Bandwidth Tools

Feature / CapabilityBoota PlatformBasic Ping / Bandwidth Tools
Sub-second TelemetryLive 1s dstat graphs & latency heatmapsDelayed average statistics
Mpps (Packets Per Second) TrackingDetailed packet rate breakdownMbps only (ignores packet rate)
Multi-Vector Bandwidth TestingUDP, TCP, SYN, and HTTP concurrent streamsSingle iPerf stream only
Global Measurement NodesMeasure latency from 50+ worldwide locationsLocal single-hop only

What Is dstat and Why Is It Essential for Stress Testing?

dstat is a versatile Linux resource monitoring tool that combines the capabilities of vmstat, iostat, netstat, and ifstat into a single real-time console. When conducting network stress tests, tracking bandwidth (Gbps) alone is insufficient: many firewalls and network switches fail due to packet rate exhaustion (Packets Per Second / PPS) or interrupt CPU saturation rather than raw gigabits. Boota integrates real-time dstat metrics to give you complete visibility.

  • Monitor softirq CPU usage caused by high network packet processing.
  • Identify packet drops at the network interface card (NIC) ring buffer level.
  • Verify TCP connection state transitions (SYN_RECV, ESTABLISHED, TIME_WAIT).

How to Interpret dstat Graphs During a Test

A healthy network server should maintain linear throughput growth without packet loss until hardware limits are reached. When running a Boota test, look for sudden drops in incoming packet rate (indicating upstream ISP filtering) or spikes in CPU wait time (indicating backend disk or database lock bottlenecks).

Frequently Asked Questions

How do I run dstat on my Linux server during a test?

You can run `dstat -ta --net --disk` or `dstat -c -m -n -g` in your terminal to see real-time CPU, memory, and network throughput statistics during your Boota test.

Why does my server crash even when bandwidth is low?

Small packet floods (e.g. 64-byte TCP SYN or UDP packets) can generate millions of packets per second (Mpps). This exhausts kernel interrupt queues and CPU softirqs without consuming significant bandwidth.

Related IP Stresser & Network Testing Guides

Ready to test your infrastructure? Start testing on Boota (Free HTTPS L7 Trial Included) — no credit card or email required.