Forking could rely on caching #746
Description
Description
Some requests are idempotent, e.g. class- or tx- or block-fetching (as long as there are no block reorders, which is highly unlikely), so they could be cached.
Rationale
Forking can lead to Devnet failing with
Failed to read from state: Error in communication with forking origin: 429 Too Many Requests. This means your program is making Devnet send too many requests to the forking origin.
1) It could be a temporary issue, so try re-running your program.
2) If forking is not crucial for your use-case, disable it.
3) Try changing the forking URL
4) Consider adding short sleeps to the program from which you are interacting with Devnet.
Caching could help reduce the number of times this issue appears.
Concern
These requests that are candidates for caching might not be the ones causing the 429 Too Many Requests error.
Impact
This would increase Devnet's memory use, and the caching layer would introduce additional time overhead.