@yaamehn DataSpreads is on pause, what is published is a proof of concept. Spreads went to a wrong direction (with generics) and is (very slowly) being redesigned. DataSpreads project depends on Spreads, no ETA...
Released zero (alpha) version of @DataSpreads. No docs yet, but there is a sample that sends and receives messages using #csharp 8.0 async streams at 14 million messages per sec accross processes. Not stable yet, but it's a matter of time to stabilize it.
Working on documentation and releases of Spreads library 1.0 and @DataSpreads alpha. Doc site template is work-in-progress, has only generated API docs now. But please subscribe to early access announcements. No spam promised, only important milestones. https://t.co/5L4kzDwd6n
It's 4 AM... During the day improved initial throughput (for 512 writers) by 70% + moved 10msec latency from 99.9% to 99.999%. This includes generic serialization, works across processes, almost ready to use as a library and has awesome absolute performance! #dotnet@DataSpreads
Utf8Json is fastest #json, all credits go to @neuecc. But with some #dotnet discipline it could be even faster. It also could read from native memory without copying and reuse buffers from pools without cleaning them for primitives. @DataSpreads now is faster. Code will be later.
@McCrews @bruinbrown93@DataSpreads I will be pushing it to 1.0 in the following months with actual production use case for trading (real time, low latency, no GC reqs) and backtesting (high throughput req). Please leave issues/comments/wishes and uncovered use cases on GitHub.