Doom in Django: testing the limits of LiveView at 600.000 divs/segundo

#1

Post by andros » Sun, Dec 28, 2025, 8:10 AM UTC

Doom in Django: testing the limits of LiveView at 600.000 divs/segundo
en.andros.dev

Re: Doom in Django: testing the limits of LiveView at 600.000 divs/segundo

#2

Post by ksec » Sun, Dec 28, 2025, 8:43 AM UTC

In the blog post it uses "600,000 divs/second!" and "10,000 divs using its template engine" while the heading uses 600.000.

I assume the difference in usage of full stop / period or comma is accidental?

Re: Doom in Django: testing the limits of LiveView at 600.000 divs/segundo

#3

Post by andros » Sun, Dec 28, 2025, 9:05 AM UTC

ksec wrote: post #2

In the blog post it uses "600,000 divs/second!" and "10,000 divs using its template engine" while the heading uses 600.000. I assume the difference in usage of full stop / period or comma is accidental?

Yes, you right hehe. I had fixed!

Re: Doom in Django: testing the limits of LiveView at 600.000 divs/segundo

#4

Post by agentifysh » Wed, Dec 31, 2025, 10:33 AM UTC

if only i could run django on cloudflare workers

guess i could run it on a dedicated server

would be nice if we can get django and liveview working without a server

Re: Doom in Django: testing the limits of LiveView at 600.000 divs/segundo

#5

Post by pawelduda » Wed, Dec 31, 2025, 10:45 AM UTC

Shame Phoenix LiveView is missing from the comparison

Re: Doom in Django: testing the limits of LiveView at 600.000 divs/segundo

#6

Post by leobuskin » Wed, Dec 31, 2025, 10:55 AM UTC

pawelduda wrote: post #5

Shame Phoenix LiveView is missing from the comparison

It's only django-related third-party packages comparison (and SSR itself), would be a bit strange to compare with a different language/stack and/or framework

Re: Doom in Django: testing the limits of LiveView at 600.000 divs/segundo

#7

Post by leobuskin » Wed, Dec 31, 2025, 10:58 AM UTC

agentifysh wrote: post #4

if only i could run django on cloudflare workers guess i could run it on a dedicated server would be nice if we can get django and liveview working without a server

you can do it on wasmer's workers, their last wasm/python approach is pretty solid (compatibility, performance). it's sad to say, but after 4 years of "beta" Python support on CF workers - it's still ugly. I dunno who was responsible for such a neglect, but even with the last changes - total fiasco

Re: Doom in Django: testing the limits of LiveView at 600.000 divs/segundo

#8

Post by kvakvs » Wed, Dec 31, 2025, 11:49 AM UTC

Since Doom renders the image with vertical columns of pixels (floor, lower wall, portal if exists continues rendering the other sector, then upper wall then ceiling) and since browsers are very good at drawing the sprites out of larger textures... You could send vertical divs shaded with the sector light level and picking the correct textures. Instead of hundreds per column you will have like 5 divs on average per column and they will be textured shaded and scaled by the browser?

Re: Doom in Django: testing the limits of LiveView at 600.000 divs/segundo

#9

Post by evilmonkey19 » Wed, Dec 31, 2025, 12:05 PM UTC

agentifysh wrote: post #4

if only i could run django on cloudflare workers guess i could run it on a dedicated server would be nice if we can get django and liveview working without a server

I wish we could host Django apps with the tasks and everything on Cloudflare workers. Also it would be nice to have a DB like SQLite within Cloudflare.

Re: Doom in Django: testing the limits of LiveView at 600.000 divs/segundo

#10

Post by rockyj » Wed, Dec 31, 2025, 12:25 PM UTC

Very impressive! Worth noting that HTMX also has a WebSocket extension - https://v1.htmx.org/extensions/web-sockets/ so one could potentially also do "live views" in more performant runtimes like JVM or Node.js