Re:600k concurrent websocket connections on AWS using Node.j...
by dylanz on Friday October 11, 2019 @09:16AM
(#21224011)
Could you explain or post a link to something about #2? I’ve never heard of that before!
[ Parent
| on HN ]
Re:600k concurrent websocket connections on AWS using Node.j...
by sciurus on Friday October 11, 2019 @10:00AM
(#21224414)
I can not. AWS, for whatever reason, does not want this publicly documented. I would write up what we learned in our testing in more detail, but I have been asked not to.
You can find some discussion of this behavior in places like https://forums.aws.amazon.com/thread.jspa?threadID=231806. I originally became aware of the issue, before hitting in production, from the HN comment at https://news.ycombinator.com/item?id=18314138
Re:600k concurrent websocket connections on AWS using Node.j...
by toast0 on Friday October 11, 2019 @02:22PM
(#21226992)
I'm glad you found my comment helpful!
I myself found out about to avoid the connection tracking in this thread https://news.ycombinator.com/item?id=15724072
It's super frustrating that Amazon doesn't document this in a more approachable manner.
Re:600k concurrent websocket connections on AWS using Node.j...
by QuinnyPig on Friday October 11, 2019 @11:29PM
(#21230460)
Their response displeases me.
Re:600k concurrent websocket connections on AWS using Node.j...
by toredash on Saturday October 12, 2019 @10:40AM
(#21233490)
This is what you need to know:
"Not all flows of traffic are tracked. If a security group rule permits TCP or UDP flows for all traffic (0.0.0.0/0) and there is a corresponding rule in the other direction that permits all response traffic (0.0.0.0/0) for all ports (0-65535), then that flow of traffic is not tracked. The response traffic is therefore allowed to flow based on the inbound or outbound rule that permits the response traffic, and not on tracking information."
Re:600k concurrent websocket connections on AWS using Node.j...
by chatmasta on Saturday October 12, 2019 @11:17AM
(#21233791)
Very interesting. It makes a lot of sense from a Linux perspective. The conntrack table requires memory, so there is some physical limit on its size. That also explains why it scales per instance type.
Re:600k concurrent websocket connections on AWS using Node.j...
by toredash on Saturday October 12, 2019 @12:02PM
(#21234140)
This is also why "endless scaling" is a fud. At some point or some level, there is either a physical, soft, standard or some kind of limit