Access Point Capacity Planning Guide

Wireless clients share a radio medium; link rate is not useful application throughput. Channel width, interference, client capabilities, slow devices and retransmissions change airtime consumption. Adding access points on the same channel can increase contention. RSSI and SNR measure different things; a strong signal does not prove low interference or sufficient capacity. Validate with intended clients, operating machinery and peak traffic, including roaming and application latency.

Link capacity differs from useful application throughput. Protocol headers, encryption, retransmissions, small files and storage waits reduce net transfer speed. Keep bits and bytes distinct: 1 Gbit/s corresponds to a theoretical 125 MB/s, not an application performance guarantee. Estimate transfer time as data size divided by measured useful throughput. Observe the network, source reads and destination writes together to locate the bottleneck. Consider temporary slowdowns and competing workloads as well as average speed.

Latency is the time between starting an operation and receiving its result. An average can hide a small number of very slow operations; medians and p95/p99 percentiles answer different questions. Network RTT, storage waits, processor queues and application processing contribute to end-to-end time. State whether measurements come from the client or server. Check whether increases coincide with traffic growth, maintenance or capacity limits. Record normal and peak-hour baselines before selecting an alert threshold.

A switch’s total PoE budget is separate from each port’s power limit. Consider device class, cable losses and startup requirements alongside port count. Power supplied by the PSE can differ from power received by the PD. An access point may boot under reduced power while disabling radios; an operational device is not proof that every feature is enabled. Recalculate the remaining budget after PSU failure, and confirm consumption and classification using management data.

Contention occurs when workloads sharing CPU, memory, storage or a link make each other wait. Apparent spare total capacity can hide a hot core or single-queue bottleneck. Correlate backup jobs, antivirus scans, index maintenance and user traffic on a common timeline. Confirm the bottleneck before adding resources. Run a workload alone and with its usual competitors to separate shared-resource effects, and report peak-hour latency alongside average utilization.

Raw capacity is not the capacity available to applications. RAID or erasure coding, filesystems, reserved space, metadata, snapshots and growth headroom are separate deductions. TB and TiB representations also change the displayed number. Write calculations with units, establish protected usable capacity, then subtract operating reserves. Track growth rate as well as current utilization. The projected exhaustion date should leave enough time to procure and deploy additional capacity.