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 sparkie on Saturday January 26, 2019 @05:47PM (#19009054)

There's a `task {}` computation expression is the FSharpx.Extras library, which makes it much more pleasant to work with TPL libraries, and removes the performance issues associated with using Async.AwaitTask etc.

[ Parent | on HN ]

Re:Memory usage of a toy C# server and client with 500K conc... by strmpnk on Saturday January 26, 2019 @05:52PM (#19009092)

Yes. That one works pretty well, though it still lags a bit behind the efficient state machines that C# generates which can also help avoid a lot of allocations and indirection in deep task chains. One step at a time though, it'd be great to see F# get a refresh around the TPL (even though it had Async first, it'd be better to align with the platform in the long run).

[ Parent | on HN ]

Re:Memory usage of a toy C# server and client with 500K conc... by platz on Sunday January 27, 2019 @12:37PM (#19012726)

This is the most current one https://github.com/rspeele/TaskBuilder.fs that Giraffe also uses.

[ Parent | on HN ]