Building a computer is only the prologue. Once it works, the real systems puzzle begins: expose where time is lost, then reshape caches, access order, buffering, prefetching, and memory layout so the machine spends less time waiting.
What real task does your product handle with GPT-6 Astra?
Maker
Von Neumann Bottleneck turns a real systems problem into an interactive one: a computer can be correct yet spend most of its time waiting for data. Players diagnose that waiting with timelines and profilers, then reduce it by changing access order, caches, buffering, prefetching, and memory layout.
GPT-6 Astra handled the repository-scale engineering needed to ship the public Alpha: tracing cross-file regressions across simulation, UI, saves, localization, and tests; auditing release blockers; designing regression checks; refining bilingual onboarding; and helping converge Windows and macOS builds. Astra is a development and release partner, not an in-game chatbot.
Report
Maker
📌
Hi Product Hunt 👋
A machine can produce the right answer and still spend much of its time waiting for data.
That invisible waiting is the subject of Von Neumann Bottleneck.
The game does begin with logic gates and a small computer, but construction is only the prologue. The real puzzle starts once the machine works. You run a design, open its timeline and profiler, and watch computation, transfers, and waiting split apart.
Then you change the system itself.
Reorder accesses. Reuse data. Add a cache. Buffer work. Prefetch what comes next. Reshape the memory layout. Run the machine again and see where the waiting moved.
Performance is not a score pasted onto a solved puzzle. Performance is the puzzle.
The current Alpha contains five regions and 40 tasks in English and Chinese. It moves from the first working machine into data transport, cache and locality, overlapping computation with transfers, prefetching, and memory layout. It is offline, deterministic, free, and open source.
GPT-6 Astra helped me turn a large work in progress into a public Alpha I could actually ship. I used it to review the Godot repository as one connected system, trace problems across files and state transitions, challenge release assumptions, plan regression checks, refine the bilingual experience, and audit the final build path.
Astra is not an in-game chatbot. Its role was closer to a systems reviewer and release engineer.
I would especially value feedback on three questions:
• When did “waiting for data” become clear as the real problem?
• Did the timeline and profiler change what you tried next?
• Where did the first ten minutes make you hesitate?
The machine works. Now find where it waits.