The attributes behind your decision
- Decision input
- Measured workload
- Primary variables
- Capacity, control, operations
- Validation
- Representative testing
- Next step
- Swiss infrastructure
Separate transfer from port speed
Monthly transfer measures total data moved over time. Port speed describes the maximum link rate. A workload can have modest monthly transfer but still require short bursts of capacity.
Estimate transfer from observable inputs
Multiply average response or media size by completed requests, downloads or viewing time. Add uploads, API traffic, backups, replication and operational overhead.
Model peaks and geographic delivery
Average monthly values hide busy hours. Estimate concurrent sessions and peak bitrate, then test from audience locations. A content-delivery network may change origin demand but does not eliminate it.
Measure and revise after launch
Track interface throughput, transfer totals, errors and application response time. Set thresholds before saturation and revise the estimate as payloads and usage change.
Worked example: concurrent video delivery
A 4 Mb/s stream delivered to 100 concurrent viewers requires approximately 400 Mb/s of payload throughput. If that demand runs for 2 hours per day over 30 days, it transfers about 10.8 TB in decimal units before protocol overhead. This assumes the full audience stays connected for every stated hour.
Port speed describes a rate; a monthly transfer allowance describes a volume. Compare both against peak and cumulative demand. Audience variation, adaptive bitrate, cache hits and distribution architecture change the estimate, so measure real events and reserve capacity for peaks instead of treating the example as a server guarantee.