Topic

Performance

8 articles

Computer Science

The architecture of a chess engine

A modern chess engine can evaluate millions of positions per second, yet most of its strength comes from surprisingly simple ideas: search, pruning, caching, and a relentless obsession with efficiency.

· 12 min read

JavaScript

Why React re-renders: understanding the Fiber work loop

Most React performance problems are really scheduling problems. A practical look at Fiber, reconciliation, and what actually happens after setState.

· 4 min read

Computer Science

Building a trading exchange in 200 lines

Modern financial exchanges move billions of dollars a day, yet the core matching engine comes down to a handful of data structures and a few unglamorous rules.

· 9 min read

Platform Engineering

Designing for sub-100ms: latency budgets in trading UIs

When a price moves, the screen has one job: show it before the trader notices the delay. A practical look at spending a latency budget across transport, processing, rendering and paint.

· 5 min read

JavaScript

Most JavaScript performance problems aren't JavaScript problems

After enough profiling sessions you start to realise the language is rarely the bottleneck. Our assumptions usually are.

· 5 min read

Architecture

Caching is easy until it isn't

Most caching strategies look brilliant during architecture reviews and become considerably less impressive the first time stale data reaches production.

· 5 min read

JavaScript

Why JavaScript performance is weird

Modern JavaScript engines are astonishingly fast, but only because they spend most of their time pretending your code is better than it actually is.

· 10 min read

JavaScript

The event loop is not what you think

Most explanations stop at the call stack and callback queue. The reality is more interesting, and explains many of the bugs engineers encounter in production.

· 4 min read

Jump to

32 articles