← Back to context

Comment by tipiirai

7 days ago

When you go pass 100k-200k records on the client side, typically fetched with event sourcing pattern, you must resort to WASM. Here's a RUST based example with 150k records to tackle the situation: https://mpa.nuejs.org/app/?rust

7 comments

tipiirai

Reply
jitl  7 days ago

The React example w/ the complicated table API will work fine for zillions of records. Virtualization is not complex math, and there are many libraries that will implement it for you in various languages.

I just tried making an array w/ 1 million items in it in my browser console `Array.from({ length: 1_000_000 }, () => ({ id: ++nextId, data: Math.random() }))` without issue. Virtualization is just simple arithmetic to select the firstRender and lastRender indexes in the array. I don't think you need WASM for this.

madeofpalk  7 days ago

> you must resort to WASM

Where does the 'must' come from? A react component will trivially handle 200k records with list virtualisation with just javascript

  • tipiirai  7 days ago

    There is an offset (depending on the app) where JS crashes with stack overflow exception, and only WASM can continue from there. On the Nue example with user records the treshold was around 150k records (only slightly depending on the browser).

    • madeofpalk  7 days ago

      What? Nue will just crash with a stack overflow if you have an array of over 150k items?

      This seems like a pretty deep flaw. It would be okay to have poor performance, but flat out crashing seems bad.

      2 replies →