←back to thread

The Bluesky firehose viewed in the style of a Windows XP screensaver

(firehose3d.theo.io)
596 points consumer451 | 2 comments | 16 Nov 24 22:07 UTC | HN request time: 0.506s | source
Show context
mbil ◴[17 Nov 24 01:29 UTC] No.42161213[source]▶
This crashes my Safari browser on iOS.
replies(7): >>42161227 #>>42161294 #>>42161301 #>>42161743 #>>42162962 #>>42163108 #>>42174356 #
yazzku ◴[17 Nov 24 01:48 UTC] No.42161301[source]▶
"Works" on Firefox if you can stomach 300-400ms pauses every 2 seconds.

Edit: I just profiled it and it spends 42% of exclusive time in texImage2D. It would be better to allocate a set of textures up front and then use glTexSubImage2D to update their contents. glTexImage2D allocates a new texture every time.

replies(1): >>42161377 #
theoretically23 ◴[17 Nov 24 02:05 UTC] No.42161377[source]▶
Thanks - should be better now hopefully on Firefox
replies(2): >>42161678 #>>42165640 #
1. yazzku ◴[17 Nov 24 17:56 UTC] No.42165640[source]▶
This did get rid of that bottleneck and the stutters are slightly better, but it still has some more work to go.

https://ibb.co/LgtJHMs

You'll want to get rid of glTexImage2D completely except for application startup (allocate a pool of N images up front, then re-use them and update with glTexSubImage2D). And short of being able to optimize the text render, which seems to be awfully stupid, you'll want to render offscreen to those textures ahead of time before you need to render them on-screen.

replies(1): >>42167286 #
2. yazzku ◴[17 Nov 24 21:10 UTC] No.42167286[source]▶
To be fair, you're crazy CPU-bound. This workload is peanuts for a modern GPU and there's no excuse for it not running at 500+ fps. But that's just how JS goes. You'd probably have better luck with C/wasm for this kind of thing if the web is your target.