[bug] Can't view resources when there are a large number of resources

[stopWarByWar]

I can not get resources of address "0x05a97986a9d031c4567e15b797be516910cfcb4156312482efc6a19c0a30c948" with error

[0xFanz]

you can change to another node RPC which is config more requests handling

[gregnazario]

Yes, looks like this page is freezing at the moment, but no longer giving that error https://explorer.aptoslabs.com/account/0x05a97986a9d031c4567e15b797be516910cfcb4156312482efc6a19c0a30c948/resources

[gregnazario]

Note: This now hangs (retrieving all the resources), instead of erroring out.

[zacharydenton]

The main bottlenecks in this page appear to be react-json-view and emotion (sx={{}}). It's possible to render all 9999 resources on https://explorer.aptoslabs.com/account/0x05a97986a9d031c4567e15b797be516910cfcb4156312482efc6a19c0a30c948/resources as (<pre>{JSON.stringify(resource)}</pre>) in about 300 ms on my machine (whereas the current implementation crashes the browser tab).

(ETA: While optimizing the page would be ideal, the pragmatic solution is of course to implement pagination.)