Summary
When loading pin.filecoin.cloud and especially when trying to show previously uploaded files, the app appears to make a very large number of JSON-RPC POST requests from the browser to GLIF. In one report, opening the page triggered more than 100 RPC requests in a short span while the UI was still loading upload history.
This is worth investigating because it makes the app feel noisy and slow, and it increases the chance of rate limiting or other RPC-provider-related failures for a fairly simple page load. Expected behavior would be a small, bounded number of RPC calls needed to initialize wallet state and load previous uploads.
Suggested repro:
- Open pin.filecoin.cloud in a browser with devtools open.
- Watch the Network panel while the app initializes and loads previous uploads.
- Note the volume of JSON-RPC
POST requests made to GLIF.
Example:
Image from slack thread:
Summary
When loading pin.filecoin.cloud and especially when trying to show previously uploaded files, the app appears to make a very large number of JSON-RPC
POSTrequests from the browser to GLIF. In one report, opening the page triggered more than 100 RPC requests in a short span while the UI was still loading upload history.This is worth investigating because it makes the app feel noisy and slow, and it increases the chance of rate limiting or other RPC-provider-related failures for a fairly simple page load. Expected behavior would be a small, bounded number of RPC calls needed to initialize wallet state and load previous uploads.
Suggested repro:
POSTrequests made to GLIF.Example:
Image from slack thread: