Memory usage of a toy C# server and client with 500K concurrent connections on

Re:Memory usage of a toy C# server and client with 500K conc... by zzzcpan on Saturday January 26, 2019 @07:24PM (#19009512)

https://en.wikipedia.org/wiki/Thread_(computing)#M:N_(hybrid...

[ Parent | on HN ]

Re:Memory usage of a toy C# server and client with 500K conc... by giancarlostoro on Saturday January 26, 2019 @07:56PM (#19009659)

Goroutines are probably closer to Fibers which D also has:

https://en.wikipedia.org/wiki/Fiber_(computer_science)

[ Parent | on HN ]

Re:Memory usage of a toy C# server and client with 500K conc... by zzzcpan on Saturday January 26, 2019 @08:15PM (#19009770)

They used to be closer to fibers years ago, when they were running on a single thread by default. Now they behave exactly like normal threads with the same problems. And fibers are threads anyway.

[ Parent | on HN ]

Re:Memory usage of a toy C# server and client with 500K conc... by giancarlostoro on Saturday January 26, 2019 @10:11PM (#19010151)

Care to share a reference to them no longer being lightweight?

[ Parent | on HN ]

Re:Memory usage of a toy C# server and client with 500K conc... by zzzcpan on Sunday January 27, 2019 @01:11PM (#19012893)

They still start with tiny stacks, if that's what you are asking. I believe it's somewhere around 2 KB nowadays.

[ Parent | on HN ]

Re:Memory usage of a toy C# server and client with 500K conc... by hu3 on Sunday January 27, 2019 @06:37AM (#19011341)

goroutines are anything but threads.

Here's a 40min talk explaining how Go's scheduler works:

https://youtu.be/YHRO5WQGh0k

[ Parent | on HN ]

Re:Memory usage of a toy C# server and client with 500K conc... by zzzcpan on Sunday January 27, 2019 @01:05PM (#19012860)

No, they are threads. It doesn't matter if they start with tiny growing stacks and whether blocking syscall wrappers call into the scheduler. Those are just implementation details.

[ Parent | on HN ]