Achieving 5M persistent connections with Project Loom virtual threads

#1

Post by genzer » Sat, Apr 30, 2022, 8:07 AM UTC

Achieving 5M persistent connections with Project Loom virtual threads
github.com

Re: Achieving 5M persistent connections with Project Loom virtual threads

#2

Post by invalidname » Sat, Apr 30, 2022, 9:13 AM UTC

This is pretty fantastic!

I'm very excited about the possibilities of Loom. Would love to have a more realistic sample with Spring Boot that would demonstrate the real world scale. I saw a few but nothing remotely as ambitious as that.

Re: Achieving 5M persistent connections with Project Loom virtual threads

#3

Post by nelsonic » Sat, Apr 30, 2022, 9:13 AM UTC

Reminds of https://phoenixframework.org/blog/the-road-to-2-million-webs... Would love to see this extended to more Languages/Frameworks.

Re: Achieving 5M persistent connections with Project Loom virtual threads

#4

Post by notorandit » Sat, Apr 30, 2022, 9:26 AM UTC

With a maximum of 64k TCP connections per single server IP, you need 77 different IP on the server side. This is a fact.

Re: Achieving 5M persistent connections with Project Loom virtual threads

#5

Post by deepsun » Sat, Apr 30, 2022, 9:32 AM UTC

How does that compare to Kotlin suspend functions?

Re: Achieving 5M persistent connections with Project Loom virtual threads

#6

Post by imperio59 » Sat, Apr 30, 2022, 9:40 AM UTC

notorandit wrote: post #4

With a maximum of 64k TCP connections per single server IP, you need 77 different IP on the server side. This is a fact.

Pretty sure you can bump that up in the kernel to hold more active connections per server that 64k...

Re: Achieving 5M persistent connections with Project Loom virtual threads

#7

Post by jauer » Sat, Apr 30, 2022, 9:41 AM UTC

notorandit wrote: post #4

With a maximum of 64k TCP connections per single server IP, you need 77 different IP on the server side. This is a fact.

How do you figure?

Clients can connect to the server on the same server port, so connection limit is more like 64k*2 for every Client IP-Server IP pair.

Re: Achieving 5M persistent connections with Project Loom virtual threads

#8

Post by peq » Sat, Apr 30, 2022, 9:43 AM UTC

notorandit wrote: post #4

With a maximum of 64k TCP connections per single server IP, you need 77 different IP on the server side. This is a fact.

Isn't this limit per client ip, server ip, and server port? (https://stackoverflow.com/a/2332756/303637)

Re: Achieving 5M persistent connections with Project Loom virtual threads

#9

Post by alanfranz » Sat, Apr 30, 2022, 9:47 AM UTC

notorandit wrote: post #4

With a maximum of 64k TCP connections per single server IP, you need 77 different IP on the server side. This is a fact.

“You need 77 ips” to do what? May be a fact or not, depending on what you’re doing.

If you suppose just one open server port, you’ll probably need 77 client ips to do this test to get unique socket pairs.

But it’s a client problem, not a server one.

Re: Achieving 5M persistent connections with Project Loom virtual threads

#10

Post by akvadrako » Sat, Apr 30, 2022, 9:47 AM UTC

jauer wrote: post #7

notorandit wrote: post #4

With a maximum of 64k TCP connections per single server IP, you need 77 different IP on the server side. This is a fact.

How do you figure? Clients can connect to the server on the same server port, so connection limit is more like 64k*2 for every Client IP-Server IP pair.

Actually every client IP+port / server IP+port pair. Linux uses 60999 − 32768 for ephemeral ports so can support 28e3^2 = 784 million connections per IP pair.