v1.9.1-1b9649f
← Back to Benchmarks

Bandwidth Throughput Benchmark

Measuring maximum bandwidth throughput for proxy connections across transfer sizes.

Scorecard

Throughput Score
84
Composite bandwidth performance across single and concurrent connections.

Methodology

  • • Controlled payloads: 1KB, 10KB, 100KB, 1MB, 10MB
  • • 1,000 sequential downloads per payload size
  • • 100 concurrent downloads for aggregate throughput
  • • Throughput calculated as bytes transferred / total time
  • • Variance measured as coefficient of variation

Metrics

Single-connection throughput: Maximum sustained download speed through a single proxy connection.
Aggregate throughput: Total bandwidth across 100 concurrent connections.
Throughput variance: Consistency of speed across repeated downloads (lower is better).
Scaling linearity: How closely aggregate throughput scales with connection count.
Last updated 2026-03-04 • 7-day window

Bandwidth Throughput Benchmark

Bandwidth throughput determines how quickly data can flow through proxy connections. For use cases involving large page downloads, media scraping, or bulk data extraction, throughput directly impacts job completion time and infrastructure costs.

Test Design

We measured throughput using controlled payloads of 1KB, 10KB, 100KB, 1MB, and 10MB through proxy connections. Each payload size was tested with 1,000 sequential downloads and 100 concurrent downloads to measure both single-connection and aggregate throughput.

Single-Connection Throughput

Hex Proxies delivered 18.5 Mbps average throughput for single-connection downloads of 10MB payloads, with peak throughput reaching 25 Mbps. For typical web page payloads (100KB-1MB), effective throughput averaged 12.8 Mbps, which is sufficient to download a full page in under 100ms.

| Payload Size | Hex Proxies (single) | Hex Proxies (100 concurrent) | Industry Avg (single) | Industry Avg (concurrent) | |-------------|---------------------|-----------------------------|-----------------------|--------------------------| | 1KB | 2.1 Mbps | 85 Mbps | 1.5 Mbps | 45 Mbps | | 10KB | 8.5 Mbps | 320 Mbps | 5.2 Mbps | 180 Mbps | | 100KB | 12.8 Mbps | 580 Mbps | 7.5 Mbps | 310 Mbps | | 1MB | 15.2 Mbps | 720 Mbps | 8.8 Mbps | 380 Mbps | | 10MB | 18.5 Mbps | 850 Mbps | 10.2 Mbps | 420 Mbps |

Aggregate Throughput

With 100 concurrent connections, Hex Proxies achieved aggregate throughput of 850 Mbps for 10MB payloads. This scales nearly linearly from single-connection performance, indicating minimal contention at the proxy gateway level. Industry averages showed sub-linear scaling, suggesting shared bandwidth pools.

Throughput Consistency

Throughput variance was measured as the coefficient of variation across 1,000 downloads. Hex Proxies showed 8% variance for 1MB payloads, compared to 22-35% for competing providers. Consistent throughput is critical for accurate job time estimation and resource planning.

Bandwidth Pricing Efficiency

At 18.5 Mbps single-connection throughput, Hex Proxies delivers approximately 2.3 GB per minute per connection. For bandwidth-priced plans, this efficiency means more data per dollar compared to providers throttling at 5-10 Mbps. Over a 1TB monthly job, the throughput advantage translates to 40-60% faster completion.

Impact on Large-Scale Operations

For operations downloading millions of pages per day, throughput directly affects infrastructure requirements. At Hex Proxies throughput levels, a 10-connection setup can process approximately 1.4 TB per day. Achieving the same throughput with slower providers would require 2-3x the connection count, increasing complexity and cost.

Compression and Transfer Optimization

Hex Proxies supports gzip and brotli compression at the gateway level, reducing actual bytes transferred by 60-80% for HTML and JSON content. Combined with high throughput, this compression support makes Hex Proxies especially efficient for text-heavy data extraction.

Steps

1
Prepare test payloads
Create controlled files at each target size on a test server.
2
Single-connection test
Download each payload 1,000 times sequentially.
3
Concurrent test
Download with 100 threads to measure aggregate throughput.
4
Compute efficiency
Calculate throughput per dollar to compare value across providers.

Tips

  • • Test with realistic payload sizes that match your actual use case.
  • • Enable compression to measure effective throughput for text-based content.
  • • Monitor throughput over time to detect throttling after high-volume usage.

Related Resources

Cookie Preferences

We use cookies to ensure the best experience. You can customize your preferences below. Learn more