During the resolution of a single query, it's possible to incur in the same web3 request twice, which is wasteful. This could happen if the user selects the balances of all to accounts in all transactions from a block, where the same account could've been the recipient of two transactions or more.
Current thinking is to evaluate DataLoader's caching facility, as it appears to be local to single queries.
During the resolution of a single query, it's possible to incur in the same web3 request twice, which is wasteful. This could happen if the user selects the
balancesof alltoaccounts in alltransactionsfrom ablock, where the same account could've been the recipient of two transactions or more.Current thinking is to evaluate DataLoader's caching facility, as it appears to be local to single queries.