3 ms·
Sorry, but even with the graphs, I'm not seeing how 1000 users continuously connected for an hour doesn't translate into a lot more server load that 1000 users
by run4yourlives 19y ago
Sorry, but even with the graphs, I'm not seeing how 1000 users continuously connected for an hour doesn't translate into a lot more server load that 1000 users polling for an hour every 10 seconds or so.
The math just doesn't add up in my head...
- gojomo 19y agoIt requires negligible (no?) traffic to keep a TCP socket 'continuously connected' when data is not being sent. (The only resource cost is the state at both endpoints remembering the socket exists.) OTOH, every 'poll' involves a lot of socket and HTTP request/response overhead traffic -- even if there's no update necessary. Still, this article overclaims the comet case. Polling is often easier to understand/implement/debug. It requires less server-side state and may be less likely to hit practical server-side implementation limits.