Coroutines are now in Clang trunk, libc++

Re:Coroutines are now in Clang trunk, libc++ by phamilton on Friday May 26, 2017 @12:07PM (#14425008)

I believe you are referring to running out of ports, as 65k available ports * 40 ~= 2M.

The limitation is actually on a quad tuple: {src_ip, src_port, dest_ip, dest_port}

As such, the actual limit is outrageously high and isn't really a problem. Interestingly enough, the referenced Phoenix benchmark overlooked the dest component and hit a limit as they had only 40 or so machines to use in the test. Had they used multiple ips on the server it would have given them a lot more breathing room.

EDIT: Multiple IPs != Multiple NICs. You can assign multiple IPs to a single physical interface. Also, they could have used multiple ports to accomplish the same effect.

[ Parent | on HN ]

Re:Coroutines are now in Clang trunk, libc++ by grogenaut on Friday May 26, 2017 @12:20PM (#14425155)

Good to know. I thought you were always limited by the outgoing port range to 65k - (used ports) good to know.

So they were limited by the testing cluster or the tested server?

[ Parent | on HN ]

Re:Coroutines are now in Clang trunk, libc++ by phamilton on Friday May 26, 2017 @01:28PM (#14425754)

They were limited by the testing cluster, but it was pointed out to them after the fact that they could have used multiple IPs or multiple ports on the tested server to go even higher.

[ Parent | on HN ]