Home › Reference › Components › Connection gateway
Connection gateway
Holds each client's connection open for the whole session on a lightweight slot. Handshakes and heartbeats take the instance's cores, and a crash drops every connection at once.
Settings
- Instance tier
- The machine size of each instance. Bigger tiers hold more open connections by default and have more CPU cores for handshakes and heartbeats.
- Instances
- How many identical gateway copies run. More instances hold more connections in total and spread out reconnect storms after a crash.
- Connections per instance
- How many open connections one instance holds. Connects above it are refused. Blank uses the tier's default.
- Handshake time
- How long setting up a new connection takes, once a core is free. Pick the shape: constant, lognormal, exponential, or uniform. Many simultaneous connects queue for cores.
- Session length
- How long a connection stays open before the user leaves. Shorter sessions mean more churn and more handshakes. Pick the shape: constant, lognormal, exponential, or uniform.
- Heartbeat every (ms)
- How often each connected client sends a keep-alive ping. Shorter intervals notice dead clients sooner but use more CPU. Blank means no heartbeats.
- CPU per heartbeat (ms)
- CPU time one heartbeat costs. Multiplied by every connected client each interval, so it adds up fast and competes with handshakes.
- Crashes
- Scheduled crashes to test failure handling. While one is active, the target refuses requests, and anything it was holding is lost.