withClaimedRewardsEras, rate limit exceeded

[ironoa]

related to #5859

api.derive.staking.query(validatorAddress,{withLedger:true, withClaimedRewardsEras: true})

seems to be so heavy that I get a RPC-CORE: queryStorageAt(keys: Vec<StorageKey>, at?: BlockHash): Vec<StorageChangeSet>:: -32999: RPC rate limit exceeded error message when I'm connected to a public endpoint. Kusama node (v1.13.0).

• If I set withClaimedRewardsEras: false it works on a Kusama public endpoint (i.e. wss://kusama-rpc.polkadot.io/), but of course I'm missing info
• I can get past to this issue when I'm connected to my internal node, withClaimedRewardsEras: true, but still it takes roughly 13 seconds for 1 address
• Polkadot doesn't seem to have the same issue: I can make the query with withClaimedRewardsEras: true set on internal and public endpoints with no problems

Not sure that's expected, so I'm opening this issue...

[TarikGul]

seems to be so heavy that I get a RPC-CORE: queryStorageAt(keys: Vec, at?: BlockHash): Vec:: -32999: RPC rate limit exceeded error message when I'm connected to a public endpoint. Kusama node (v1.13.0).

As you mentioned I would imagine this is directly related to the public node you are connected to. For all the heavy calls we are using entries to get everything at once so there is no limit hit. Have you tried with other Kusama public nodes?