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.
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
