# Throughput

Throughput is the volume of data a proxied connection can move per second, bounded by the slowest link on the path: for residential exits the household's upload and download speed, for mobile exits the cell, for datacenter and ISP exits the facility uplink. Aggregate throughput grows with concurrency, so a pool can move large volumes even when each exit is modest; per-connection throughput is what matters for large files and media.


## Rule of thumb

| Exit type | Per connection | Best use |
| --- | --- | --- |
| Datacenter | Hundreds of Mbit/s | Bulk transfer, large files |
| ISP | Hundreds of Mbit/s | Long sessions with heavy pages |
| Residential | A household line: a few to tens of Mbit/s | Pages, APIs, many parallel connections |
| Mobile | Cellular: variable | Pages and apps, not bulk |


## Throughput and the bill

On per-GB networks, moving more bytes faster only makes the bill arrive sooner. Throughput is a question for datacenter and ISP products; on residential and mobile the question is cost per byte.


## How it works at ProxShift

ProxShift sets no throughput cap on any network; datacenter and ISP addresses run at wired speed, residential and mobile at the speed of the household or cell behind the exit.

Source: https://proxshift.com/glossary/throughput