How a Microsecond-Level Low-Latency Engine Works

8 pointsposted 2 days ago
by CrazyTomato
(medium.com)

5 Comments

pixelpoet

an hour ago

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 :)

RobRivera

37 minutes ago

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.

jeffbee

an hour ago

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.

laweijfmvo

an hour ago

i'm still trying to figure out why the Eiffel tower is featured in the first graph

hylaride

an hour ago

This article feels like it was "expanded" with an LLM.