Open soc1c opened 5 years ago
That's pretty curious, it's definitely built to withstand that. It's already only rendering the rows in the list that are within the viewport, so that shouldn't be a problem with the number of nodes. 99% it's a memory leak/bloat, those are always fun in JS :P, I'll see what I can do.
Reproduced - after running telemetry all night the site was still updating, however it would take a long time to update rendering when scrolling. Profiling results:
The red GC pauses are each ~11ms, which is odd since the actual Web Content process doesn't seem to spike in memory at all.
Was able to reproduce this again. Let me know if there is anything I can provide.
I believe this is fixed, @maciejhirsz ?
For Kusama with ~150 nodes reporting to the dashboard by default, it keeps freezing my Firefox 68.0.1 (64-bit) on Archlinux after running it a couple of hours.
Maybe it's worth investigating some kind of filters, i.e., only show the top 50 nodes with lowest latency.
ref https://github.com/paritytech/polkadot/issues/416