csot '26/low-latency systems track

Same feed.
Network ingest.

Week 5 is the capstone network gateway: receive the fixed wire-format tick stream over UDP, run the Week-1 z-score strategy, pass the order-stream determinism gate, then compete on wall-clock run time and throughput on the same held-out feed, on the same machine.

Week 5 reference · ships with judge
full feed run
45,128,383,654ns

wall-clock replay of the held-out tick feed

throughput
4.432M ticks/s

ticks processed per second on the judge machine

How it works

Five steps from sign-in to leaderboard.

  1. 01

    Read the project brief

    Week 5 ships the same binary tick feed as Week 4 and the same canonical order stream. Your gateway must match the reference order-for-order first.

  2. 02

    Implement create_gateway

    One translation unit: gateway.cpp. Threads are allowed — ingest over UDP, hand ticks to the strategy, and merge to one ordered order stream.

  3. 03

    Submit gateway.cpp

    Drop your single gateway.cpp on the dashboard. The judge compiles it with threads enabled and queues evaluation automatically.

  4. 04

    Correctness, determinism, then time

    The judge diffs your order stream against the answer key, then runs the same feed K times. A race means no rank — fix it before you tune.

  5. 05

    The leaderboard updates

    Score ranks wall-clock run time and throughput once reference denominators are captured on the judge machine.

Week 5 · project submission · repo links open

Share your public repo

Week 5 · network gateway. Public repo link submissions are open until 23:59 IST on Sunday 12 July. You can update your URL until then. A place on the gateway leaderboard required a correct, deterministic gateway.cpp evaluated while rankings were open.

Direct link: /#week5-project

Submit a public GitHub or GitLab URL with your Week 5 network gateway project for cohort review. This is separate from uploading gateway.cpp on the dashboard.

Before you submit

  • Public repo on GitHub or GitLab — private repos cannot be reviewed.
  • Your gateway.cpp, shipped headers, tick generator, and local harness sources.
  • Root README with build steps, thread count, ingest notes, and headline throughput numbers.
  • Include data/gen_feed.py; do not commit large *.feed streams.
  • .gitignore should cover build/ and generated streams.

Loading…

Week 5 · network gateway

Live gateway board

Week 4 pipeline hall of fame on the pipeline tab; Week 3 aggregator on the aggregator tab; Week 2 cache on the cache tab; Week 1 final top 37 on the archived tab.

Full leaderboard →
01
···
loading
02
···
loading
03
···
loading