WebRTC Metrics
A comprehensive overview of WebRTC statistics, derived calculations, extracted features, and observable signals, to better understand call quality, connectivity, and user experience in rtcStats
On this page3 sections
Too many local ICE candidates
Last updated Applies tortcstats-enrichmentrtcstats.com
Having more than 20 local ICE candidates can overwhelm ICE gathering and connectivity checks. This may slow down connection setup and waste browser resources. Keep the local candidate count small and only collect what is necessary for your network paths.
Description
Having more than 20 local ICE candidates can overwhelm the ICE gathering process. This may slow down connection setup and increase browser resource usage as ICE checks are performed across too many candidate paths.
What do we do here?
We count the number of local ICE candidates collected for any peer connection. If the total exceeds 20, the observation is raised.
Our suggestions
- Reduce the number of local ICE candidates collected by your client.
- Prefer only the candidate types you need for your expected network environment.
- Use server-side or browser-side candidate filtering when appropriate to avoid unnecessary candidate flooding.
