3 ms·
Yeah, it definitely feels sluggish, so I assumed it was bugging out. It started pretty snappy and then slowed way down. Ping tester says somewhere between 50 a
by catapart 4y ago
Yeah, it definitely feels sluggish, so I assumed it was bugging out. It started pretty snappy and then slowed way down.
Ping tester says somewhere between 50 and 75ms to Amazon's Virginia center.
- amalgamated_inc 4y agoI think it ran out of memory and the BEAM crashed and restarted. Gave it a bit more memory, hoping it'll hold out haha
- catapart 4y agoHa ha! Nice. Yeah, I saw on another comment that you're apparently running this with SSR, which is pretty crazy, to me! I'm surprised it's as snappy as it is, honestly, but the lag makes a lot of sense, now. Also shocked that you'd want to incur that much bandwidth cost - assuming you're being charged for it. Something like this should be able to run in the client effortlessly, so I would think even experimenting with SSR, you'd want to do most of the processing client side and then just dribble in the server re-renders, for more batched processing. In any case, good job! Definitely does the thing you set out to do with it, and is a clear demonstration of SSRs capabilities (and current weaknesses).