|
If I use the Websocket app to allow clients to connect, is there a limit to the number of simultaneous connections on either shared or cloud hosts? If the limit is exceeded, what happens? Are the web socket connections reclaimed or closed out automatically even when clients abort connections, or is this the responsibility of the server app e.g. Node.js? asked 05 Jan '16, 23:53 pixelglow |
|
There is no limit in the number of hosts, obviously other resources such as RAM and CPU usage will limit the number, but we do not monitor or throttle it directly. The connection will stay open as long as the app keeps it open. answered 06 Jan '16, 06:38 johns ♦♦ Doesn't the host have some open file or socket limit? And if I'm on a shared host is that open file or socket limit then shared with all the other people using it?
(06 Jan '16, 23:27)
pixelglow
|
|
The number of websocket connections is indeed limited by the system open files limit. If the limit is reached, Nginx may stop responding to requests intermittently, or completely. We have that set to a very high value for the system nginx user, so its unlikely that the limit will be reached. If it does, we'll be alerted by our monitoring systems and will take immediate action to ensure that the responsible customer doesn't disrupt service for the other customers on the shared server. answered 07 Jan '16, 01:17 seanf What's the limit approximately? How about cloud servers, do they have a single limit instead of a shared limit?
(07 Jan '16, 08:38)
pixelglow
The limit is 150000 on all of our servers. Our cloud servers are dedicated VPS boxes, so on those machines you're not sharing that limit with other customers.
(07 Jan '16, 17:24)
seanf
|
