CWSS study materials
CWSS study resources

Auditorium Overload: Twelve APs for 4,500 Devices

CWSS · Put your knowledge to work in context.

All case studies

Auditorium Overload: Twelve APs for 4,500 Devices

A 2,200-seat auditorium hosts product launches attended by 1,500 people, each carrying a laptop and two phones. The WLAN has 12 ceiling-mounted dual-radio APs, all on 80 MHz in 5 GHz, broadcasting six SSIDs (corporate, guest, events, IoT/AV, staff, legacy). 2.4 GHz runs at full power with 1, 2, 5.5 and 11 Mbps rates enabled. At the last event, clients associated successfully but page loads timed out, the organizer's livestream failed, average throughput per client fell below 100 kbps, and 5 GHz channel utilization reached 95%. The AV team reports wireless microphones dropping out during sessions. The next event is in eight weeks, and the venue will not run new cabling, so the AP count is capped at the existing drops unless cabling is funded.

1. Do the capacity math and state what the 12-AP design can and cannot support.

Read the worked answer

Device load: 1,500 attendees × 3 devices = 4,500 clients. Across 12 APs that is 375 clients per AP, or roughly 190 per radio - far beyond any usable design.

Use airtime, not association count, as the real limit. A realistic planning target for mixed voice, video and data in a dense venue is about 30–50 actively transmitting clients per radio, with a hard ceiling near 100 associated clients per radio. Twelve APs give 24 radios, so the practical ceiling is roughly 700–1,200 associated clients and far fewer active ones. This design cannot serve 4,500 devices with any interactive experience, regardless of configuration tuning.

Seat-based sizing is a useful cross-check: one AP per 50–75 seats in a high-density auditorium means roughly 30–44 APs for 2,200 seats. The 12-AP design is therefore short by a factor of two to four.

The honest answer to the organizer: configuration changes will improve fairness and stability, but they will not turn 12 APs into a venue for 4,500 devices. Either fund additional cabling and APs, or cap attendance devices - for example one registered device per attendee, with a controlled guest onboarding process - and set expectations in writing.

2. Assuming the cabling debate continues, what configuration changes do you make now, and what does each fix?

Read the worked answer

Tune for airtime efficiency, not peak rate:

  • Move 5 GHz to 20 MHz. 80 MHz channels give at most a handful of non-overlapping channels and put every neighboring AP into co-channel contention; 20 MHz multiplies reuse and shortens frame airtime per transmission, which is what dense venues need.
  • Disable 1, 2, 5.5 and 11 Mbps on 2.4 GHz and drop beacon and management overhead by removing unnecessary rates; low rates consume enormous airtime per frame and let distant clients drag down the cell.
  • Cut the SSID count. Six SSIDs means six beacon sets per AP and more probe traffic. Keep guest, events and IoT/AV, and fold staff and legacy into those or retire them. Map each remaining SSID to a clear purpose.
  • Turn off or heavily reduce 2.4 GHz unless a required device is 2.4-only; the band cannot absorb 4,500 clients.
  • Enable band steering, airtime fairness and multicast-to-unicast conversion. Multicast video and discovery traffic otherwise broadcasts at the lowest rate to every client.
  • Apply per-client bandwidth limits and connection limits on guest, and rate-limit or block peer-to-peer traffic.

Measure before and after with channel utilization, retry rate and per-client throughput; publish the numbers so the cabling decision is made on evidence.

3. Why are the wireless microphones dropping out, and how do you resolve that alongside the Wi-Fi changes?

Read the worked answer

Professional wireless microphones normally operate in UHF TV bands (roughly 470–698 MHz) and are not affected by 5 GHz Wi-Fi. Dropouts there point to a different cause: TV channel repacking, intermodulation between microphone channels, antenna distribution problems, or simply low RF level at the receiver. But some systems - including many compact digital and conference systems - use 2.4 GHz or 900 MHz, and those absolutely collide with full-power 2.4 GHz APs and with 4,500 client radios.

Resolution sequence:

  1. Identify the exact microphone model and frequency band from the AV team's inventory. Do not guess.
  2. If they are UHF: perform a spectrum scan of the venue's TV band, coordinate frequencies, and check receiver antenna placement and cabling. Wi-Fi changes will not help, and lowering Wi-Fi power will not fix an intermodulation problem.
  3. If they are 2.4 GHz digital: treat them as a protected, latency-sensitive system. Scan 2.4 GHz, reserve a channel for the microphones, and pin the venue's remaining 2.4 GHz APs away from it or disable 2.4 GHz in the hall. Prefer moving the microphones to a licensed UHF system for the next event if budget allows.
  4. Re-test during a full rehearsal with the Wi-Fi network at event load, because interference only appears under real conditions.