"Solve Garbage Collection in C# for HFT · $10.00 raised of est. $200.00 target"
This can't be serious.
Broader point I am making is, what differentiates genuine ideas from the token burn? What happens when the pool exhausts but the task is not done?
lol saw that one too
"A thorough written survey of why .NET garbage collection causes latency spikes in HFT contexts"
i'm like, dude, just rewrite in Zig if you want that control back, not all of your compute goodies will come from Redmond
From my 10 years in the .net, it seemed C# devs will pretty much do anything to avoid using the right tool for the job or solving the immediate problem at hand.
You keep putting money into the slot and pulling the lever
The sarcastic solution is to use C# bindings to a non-GC language. Put all available memory under control of a pool allocator and enjoy the perf gain.
market decides - just like kickstarter
It indicates the level of trust people have in the platform, and the combination of the product-platform behavior. If someone with the wherewithal to solve garbage collection for C# for HFT could actually describe why GC in C# was a problem, they wouldn't be asking for $10. But for $10, for something something you're dimly aware of is a problem? I'd throw $10 at some nonsense I read on the Internet.
> What happens when the pool exhausts but the task is not done?
Have a stupider LLM aggregate similar questions.
It's already solved (by humans) for Java, which can now be used for HFT. It seems like it's possible to do for C#.