News for hackers. Stuff that matters.
Re:How a Microsecond-Level Low-Latency Engine Works by jeffbee on Wednesday June 24, 2026 @02:41PM (#48664049)
That certainly is a bag of words. I'll congratulate anyone who can convincingly explain why the TCMalloc design diagram is in this blog post.
Re:How a Microsecond-Level Low-Latency Engine Works by laweijfmvo on Wednesday June 24, 2026 @03:03PM (#48664322)
i'm still trying to figure out why the Eiffel tower is featured in the first graph
Re:How a Microsecond-Level Low-Latency Engine Works by hylaride on Wednesday June 24, 2026 @03:07PM (#48664363)
This article feels like it was "expanded" with an LLM.
Re:How a Microsecond-Level Low-Latency Engine Works by pixelpoet on Wednesday June 24, 2026 @03:06PM (#48664356)
I was hoping for something more like,

"To overcome these self-inflicted challenges, DolphinDB stopped hiring noob developers trying to make HFT systems in Python, instead preferring run-of-the-mill C/C++ developers who understand heap vs stack allocation".

Edit: oh wow, check the poster's previous submissions :)

Re:How a Microsecond-Level Low-Latency Engine Works by RobRivera on Wednesday June 24, 2026 @03:22PM (#48664541)
Thanks for saving me a read.

I love the open-ended nature of the title tho.

It doesn't say how an effective, efficient, nor industrial low-lantency engine works, nor what a microsecond level engine is (insofar as a label cutoff).

Honestly, boring heap/stack practices with mindfulness about the application workflow and memory management therein goes miles.