News for hackers. Stuff that matters.

A comment on Maintaining 65k open connections in a single Ruby process. Parent comment

Re:Maintaining 65k open connections in a single Ruby process by john37386 on Monday October 29, 2018 @06:33PM (#18332219)
I'm sure that your ruby can hold +100k connctions with enough RAM.
[ Parent | on HN ]
Re:Maintaining 65k open connections in a single Ruby process by WJW on Monday October 29, 2018 @06:39PM (#18332270)
I ran 4 `ab` processes against it, each with 20k concurrent connections, so the maximum amount of connections "should" have been 80k. The fact that the actual number was so close to 65536 makes me very suspicious that there is some kernel level thing at play here. I agree that the ruby program can probably scale up much more with enough RAM.
[ Parent | on HN ]
Re:Maintaining 65k open connections in a single Ruby process by andrewmackrodt on Tuesday October 30, 2018 @12:21PM (#18338272)
Would this have been affected by the number of available ports on your single loopback address, assuming 127.0.0.1. You'd have to connect via multiple network devices.

Edit: comment below clarifies servers.

[ Parent | on HN ]
Re:Maintaining 65k open connections in a single Ruby process by john37386 on Monday October 29, 2018 @06:45PM (#18332330)
Was iptables running? Maybe they hit a conntrack limit
[ Parent | on HN ]
Re:Maintaining 65k open connections in a single Ruby process by tyingq on Monday October 29, 2018 @06:51PM (#18332373)
What does ulimit -a say?
[ Parent | on HN ]