HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
PIYUSH-KUMAR1809
order-matching-engine
C++2025–2026
PIYUSH-KUMAR1809 / order-matching-engine

order-matching-engine

High performance order matching engine

2Distinct people
4Mentions
0Explicit recommenders
169GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

High performance order matching engine

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by day4 dated mentions

Observed mentions: 2025-12-13 15:13:47 UTC to 2026-01-07 01:42:42 UTC.

012025-12-13 00:00:00 UTC to 2025-12-14 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsDec 132025-12-14 00:00:00 UTC to 2025-12-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-15 00:00:00 UTC to 2025-12-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-16 00:00:00 UTC to 2025-12-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-17 00:00:00 UTC to 2025-12-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-18 00:00:00 UTC to 2025-12-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-19 00:00:00 UTC to 2025-12-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-20 00:00:00 UTC to 2025-12-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-21 00:00:00 UTC to 2025-12-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-22 00:00:00 UTC to 2025-12-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-23 00:00:00 UTC to 2025-12-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-24 00:00:00 UTC to 2025-12-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-25 00:00:00 UTC to 2025-12-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsDec 252025-12-26 00:00:00 UTC to 2025-12-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-27 00:00:00 UTC to 2025-12-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-28 00:00:00 UTC to 2025-12-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-29 00:00:00 UTC to 2025-12-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-30 00:00:00 UTC to 2025-12-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-31 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2026-01-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-02 00:00:00 UTC to 2026-01-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-03 00:00:00 UTC to 2026-01-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-04 00:00:00 UTC to 2026-01-05 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-01-05 00:00:00 UTC to 2026-01-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-06 00:00:00 UTC to 2026-01-07 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-01-07 00:00:00 UTC to 2026-01-08 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJan 7

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Dec 132025-12-13 00:00:00 UTC2025-12-14 00:00:00 UTC110
Dec 142025-12-14 00:00:00 UTC2025-12-15 00:00:00 UTC000
Dec 152025-12-15 00:00:00 UTC2025-12-16 00:00:00 UTC000
Dec 162025-12-16 00:00:00 UTC2025-12-17 00:00:00 UTC000
Dec 172025-12-17 00:00:00 UTC2025-12-18 00:00:00 UTC000
Dec 182025-12-18 00:00:00 UTC2025-12-19 00:00:00 UTC000
Dec 192025-12-19 00:00:00 UTC2025-12-20 00:00:00 UTC000
Dec 202025-12-20 00:00:00 UTC2025-12-21 00:00:00 UTC000
Dec 212025-12-21 00:00:00 UTC2025-12-22 00:00:00 UTC000
Dec 222025-12-22 00:00:00 UTC2025-12-23 00:00:00 UTC000
Dec 232025-12-23 00:00:00 UTC2025-12-24 00:00:00 UTC000
Dec 242025-12-24 00:00:00 UTC2025-12-25 00:00:00 UTC000
Dec 252025-12-25 00:00:00 UTC2025-12-26 00:00:00 UTC000
Dec 262025-12-26 00:00:00 UTC2025-12-27 00:00:00 UTC000
Dec 272025-12-27 00:00:00 UTC2025-12-28 00:00:00 UTC000
Dec 282025-12-28 00:00:00 UTC2025-12-29 00:00:00 UTC000
Dec 292025-12-29 00:00:00 UTC2025-12-30 00:00:00 UTC000
Dec 302025-12-30 00:00:00 UTC2025-12-31 00:00:00 UTC000
Dec 312025-12-31 00:00:00 UTC2026-01-01 00:00:00 UTC000
Jan 12026-01-01 00:00:00 UTC2026-01-02 00:00:00 UTC000
Jan 22026-01-02 00:00:00 UTC2026-01-03 00:00:00 UTC000
Jan 32026-01-03 00:00:00 UTC2026-01-04 00:00:00 UTC000
Jan 42026-01-04 00:00:00 UTC2026-01-05 00:00:00 UTC110
Jan 52026-01-05 00:00:00 UTC2026-01-06 00:00:00 UTC000
Jan 62026-01-06 00:00:00 UTC2026-01-07 00:00:00 UTC110
Jan 72026-01-07 00:00:00 UTC2026-01-08 00:00:00 UTC110

What Hacker News says

4 sources

Show HN: Market Processing Engine in C++20 (150M orders/SEC)

Author here. This started as a quest to see how fast I could push a single core on an M1 Pro. I built an order matching engine from scratch using C++20. Initially, it did ~100k ops/sec. After a month of optimization, it now does ~156M ops/sec. Key optimizations: - Removed all mutexes (Shard-per-Core architecture). - Custom lock-free SPSC Ring Buffer for thread communication. - Replaced std::map with flat vectors + bitset scanning (using CTZ intrinsics). - Zero-allocation hot path using std::pmr (Polymorphic Memory Resources) on the stack. To prove it handles real markets (not just random numbers), I verified it by replaying captured Binance L3 market data (132M ops/sec). Detailed write-up of the optimization journey here: https://medium.com/@kpiyush8826/how-i-optimized-a-c-matching... Happy to answer questions!
2 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.