Teleport Proxy memory overhead during high-throughput TTY session recording

The Teleport identity-aware proxy manages concurrent TCP connections and streams TTY output to backend storage providers. While resource cleanup is tied to certificate expiration or session termination, the memory footprint of the proxy process scales with the number of active sessions.

When handling high-throughput TTY streams, there is uncertainty regarding the specific memory overhead per concurrent session and how the proxy buffers data before it is committed to the storage backend (such as S3 or GCS).

• What is the expected resident set size (RSS) increase per active session when recording high-volume TTY output?
• Does the proxy employ a fixed-size buffer per session, or does memory allocation scale based on the throughput of the stream?