3 ms·
This is pretty slick. On the demo page, you might consider dropping the number of rows by default from 10,000 to 1,000. Though Zapper's rendering handles it v
by rhencke 8y ago
This is pretty slick.
On the demo page, you might consider dropping the number of rows by default from 10,000 to 1,000. Though Zapper's rendering handles it very quickly, the browser struggles a bit to keep up in Chrome and FF. It gives a pretty snappy experience doing live-typing editing at 1,000 though.
- cup-of-tea 8y agoIt's pretty fast for me at 10k rows. Maybe you're doing something different.
- coder543 8y agoIt varies from computer to computer. I could definitely see an older/weaker computer struggling with rendering the output from 10k rows, even with the truncation I implemented, but I wanted it to render enough rows that it could actually measure how long it took with some accuracy by default. The Spectre attack mitigations mean that browsers only provide 2ms to 3ms resolution on their JavaScript/WASM timers now, which makes the measurement accuracy very rough in WASM unless the operation being measured takes a few tens of milliseconds.