Open Horusiath opened 8 years ago
That's a cardinal sin of majority of .NET tooling. When you take a look at WCF buffer management which has been copied to the Azure library, it's again a pool of byte arrays, which is wrong as well. Can you link to the MS version of it? So far, the most reasonable one was the one in EventStore.
Also see ASP.Net's KestrelHttpServer memory pool, I know those guys are very perf happy:
Currently our seialization/deserialization relies on
byte[]
. I think we could improve this overtime by starting to use managed buffer pools directly.Right now we have many implementations of byte buffers (3 different ones in Akka.IO, Helios and Google.ProtocolBuffers + 1 incoming with DotNetty), but I've seen that MS is working on some common managed buffers package. And even without it we could speak with Azure team and J. Skeet about moving our implementations into one separate package to follow single standard.