News for hackers. Stuff that matters.

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

Re:Memory usage of a toy C# server and client with 500K conc... by coder543 on Saturday January 26, 2019 @08:16PM (#19009777)
Do those channels support async? Since C# is built around async/await for scaling to large numbers of connections / tasks, they wouldn't be very useful if they didn't support async, but I'm not familiar enough with modern C# to figure out if they do or not.
[ Parent | on HN ]
Re:Memory usage of a toy C# server and client with 500K conc... by manigandham on Saturday January 26, 2019 @08:27PM (#19009818)
Yes. It's a library that is fully async. We process millions of records/second using these.
[ Parent | on HN ]
Re:Memory usage of a toy C# server and client with 500K conc... by noir_lord on Sunday January 27, 2019 @01:43PM (#19013074)
Do you happen to have any public information on this approach, it sounds interesting but I'm not up on the C# world like I used to be.
[ Parent | on HN ]
Re:Memory usage of a toy C# server and client with 500K conc... by manigandham on Sunday January 27, 2019 @02:43PM (#19013402)
This is the best overview article so far: https://ndportmann.com/system-threading-channels/
[ Parent | on HN ]
Re:Memory usage of a toy C# server and client with 500K conc... by noir_lord on Sunday January 27, 2019 @02:53PM (#19013451)
Thank you.
[ Parent | on HN ]
Re:Memory usage of a toy C# server and client with 500K conc... by benaadams on Saturday January 26, 2019 @08:28PM (#19009826)
Yeah you have a triple for different use cases; the sync call is `TryRead` so its non-blocking; `ReadAsync` for async reading and `WaitToReadAsync` to wait for data to be available without reading (likely then followed by the non-blocking `TryRead` in usage)
[ Parent | on HN ]