Switch Port Capacity
Calculate switch port capacity requirements and oversubscription ratios.
About Switch Port Capacity
A switch is 'non-blocking' when its internal fabric/backplane capacity is at least as large as the combined bandwidth demand of all ports running at full duplex simultaneously — meaning every port can run at line rate at the same time with zero contention. When fabric capacity is lower than total port demand, the switch is 'blocking' or oversubscribed at that ratio, meaning ports must share the internal fabric and won't all reach line rate simultaneously under full load. Oversubscription is a deliberate, common design choice for access-layer switches where all ports rarely peak simultaneously — but it becomes a real bottleneck if traffic patterns don't match that assumption.
Formula
Oversubscription ratio
ratio = (ports × speed × 2) / fabric_capacity
- \times 2
- full-duplex (send + receive)
Worked example
With the default values below, Switch Port Capacity returns Oversubscription Ratio of 4. Change any input above and every figure here is recalculated in your browser.
Inputs used
- Number of Portsminimum 1
- 48
- Port Speedminimum 0.1 Gbps
- 10 Gbps
- Switch Fabric / Backplane Capacityminimum 1 Gbps
- 240 Gbps
Results
- Oversubscription Ratio
- 4
- Total Port Bandwidth Demand (full duplex)
- 960.0 Gbps
- Effective Bandwidth per Port Under Full Load
- 2.50 Gbps
Step by step
- 1Values used
- 2Oversubscription ratio
- 3Oversubscription Ratio= 4
- 4Total Port Bandwidth Demand (full duplex)= 960.0 Gbps
- 5Effective Bandwidth per Port Under Full Load= 2.50 Gbps
Assumptions and limits
- The result is derived only from the 3 inputs listed above. Anything not among them is not part of the calculation.
- In particular, this calculator does not take inflation, tax, fees or charges or compounding frequency into account.
- Figures are rounded for display to 2 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.
How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.
Frequently Asked Questions
Is an oversubscribed (blocking) switch always a problem?
Not necessarily — access-layer/edge switches are commonly designed with 2:1 to 4:1 oversubscription because real-world traffic rarely has every port at 100% simultaneously. Oversubscription becomes a genuine bottleneck mainly for uplinks, aggregation-layer switches, or workloads (like storage networks) where sustained near-line-rate traffic on many ports at once is expected.
What's a typical oversubscription ratio for a core switch?
Core and spine switches are usually designed as non-blocking (1:1 or better) since they aggregate traffic from many access switches and a bottleneck there affects the whole network — access switches more commonly run 3:1 to 8:1 oversubscribed.
How is effective bandwidth per port calculated when oversubscribed?
It's the rated port speed divided by the oversubscription ratio, representing the average bandwidth each port could sustain if all ports demanded traffic simultaneously and the fabric fairly shared its capacity — actual per-port throughput in practice depends on the switch's scheduling/QoS behavior and real traffic patterns.
