Never got my fans spun up even on an old MacBook, so I assumed everything was peachy, but there were some wins to be had. I was doing a small amount of parsing during the "typing" effect to prevent small glimpses of styling syntax from showing up, and found some wins there. Also cut down the number of particles in the intro animation, though that's a Svelte component that's being destroyed once you start.
Simply having the page open makes my GPU fans spin to max, and the whole page lags. The text stutters, the orange particles at the start are a slideshow, etc. Task manager shows my GPU "3D" processing at 100% for some reason, even though the page seems to be almost entirely text?
Windows 10, Firefox. Nvidia GPU. Not sure whats happening.
That's interesting. I'm on a 12 year old macbook (macOS, Chromium, Intel HD4000 iGPU) and it runs perfectly fine. Everything's smooth, including the particles at the beginning.
Thanks. I guess it's slightly improved? The orange particles at startup improved from 1fps to maybe 2fps. Opening the devtools locked up the whole browser for a solid 10 seconds.
I'm not totally sure what's going on here. My typical profiling techniques show almost all the time going into "ZwUserMsgWaitForMultipleObjectsEx" in a non-js stack frame. I don't really understand what that means.
Anyway, something is up, and I don't really know what it is. The UI of the actual app still intermittently locks up for seconds at a time.
Never got my fans spun up even on an old MacBook, so I assumed everything was peachy, but there were some wins to be had. I was doing a small amount of parsing during the "typing" effect to prevent small glimpses of styling syntax from showing up, and found some wins there. Also cut down the number of particles in the intro animation, though that's a Svelte component that's being destroyed once you start.
Thanks for flagging.