#Preview CRDs

1 messages · Page 1 of 1 (latest)

silver hawk
#

Hey, cool! At the time that I ran into the slowness, it was parsing many tens of megabytes of JSON in the frontend, streamed over our GraphQL API. And because it was streaming, and WASM is single-threaded, you could really feel every little pause as it parsed a new chunk. So, might just be a question of how much JSON is being parsed and how frequently. Wish I kept the pprof screenshots.

For comparison, we did this same thing in JS and it was "fine" aside from needing to download so much data in the first place. My main takeaway was just that browsers are really really good at parsing JSON natively.