DoomBench – Can Your Data Stack Run Doom?
The article discusses the DOOMBench project, which tests various data stack architectures by running a multiplayer DOOM server entirely in SQL. It highlights the challenges of balancing analytical performance and transaction processing in database systems. The project builds on a previous initiative called DOOMQL, showcasing how databases can handle game mechanics and player interactions in real-time.
- ▪DOOMBench serves as a stress-test for different data stacks by running a multiplayer DOOM server in SQL.
- ▪The project emphasizes the difficulty of optimizing databases for both analytical and transactional workloads.
- ▪DOOMQL, the precursor to DOOMBench, utilizes recursive CTEs for rendering and a client-server architecture for player inputs.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Cedardb |
| Canonical URL | https://cedardb.com/blog/doombench/ |
| Publication time | Tue, 26 May 2026 16:53:26 +0000 |
| Retrieval time | 2026-05-26T17:07:50.079Z |
| Last seen | 2026-05-26T17:07:50.079Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | mt7WUc7q4q9m |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Can Your Data Stack Run DOOM?TL;DRWe ran a multiplayer DOOM server in pure SQL on different data stack architectures, recorded nice videos, and measured what breaks first.Click here to go directly to the benchmark page (with videos).Here is a video of CedarDB being “DOOMbench”-ed: Your browser does not support the video tag.Why DOOM?Pedantic note: The original DOOMQL uses raycasting, not BSP trees, making it technically more Wolfenstein than DOOM as some people pointed out.Last year, we published DOOMQL: a multiplayer DOOM-like game running entirely inside SQL, using recursive CTEs for raycasting and a real client-server architecture where players connect directly to the database. We were very excited when it hit the front page of Hacker News.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Cedardb.
Discussion
0 commentsMore from Cedardb
