Intermittent 'Connection pool exhausted' messages in Source Engine multiplayer

Goal: diagnose intermittent connection pool exhaustion when using SteamNetworkingSockets in Source Engine multiplayer, focusing on identifying whether failures stem from pool limits versus other network issues.

Constraints: the pool size is not exposed via console variables, defaults differ between engine builds, and SteamNetworkingConfig fields that affect it are undocumented; enabling debug output requires setting a custom debug callback, which may be restricted by anti‑cheat systems. Uncertainty remains about the exact threshold at which exhaustion occurs and which config values most effectively raise that threshold.

What is the default connection pool size for SteamNetworkingSockets in the current Source Engine build?

How can one measure current pool utilization without modifying engine source or violating anti‑cheat restrictions?

Which SteamNetworkingConfig parameters most directly influence the exhaustion threshold under typical multiplayer load?