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.

Similar solution worked for ASP back in 1999. ASP/VBS was terrible slow at string building and Response.Write. Build it in the fast code and then output.

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.

You keep putting money into the slot and pulling the lever

Real question is, how do you get press for this site after this falls off HN?

But at least collectively pulling it :-)

While standing around in a circle

market decides - just like kickstarter

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.

C# and Java devs are anecdotally the only kind of dev to think of themselves primarily by language.

Most other devs don’t talk about language in a driest few sentences intro.

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

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#.

I think assumption of the gp is that while Fable might be impressive, even Fable would take a bit more (sarcastically meaning a lot more) than $200 of tokens to solve this quite serious problem.

Yes, this is the "LMAX Disruptor": https://lmax-exchange.github.io/disruptor/user-guide/index.h...

You can write only-stack-alloc or limited-alloc C#, and Microsoft have put a lot of work into it (Span etc); it's just a bit unidiomatic.

Mind you, the last time I had contact with HFT it was inside an FPGA context..