Skip to content
This repository has been archived by the owner on Jul 16, 2024. It is now read-only.

Accounts with too many objects can reach rpc rate limit #127

Open
Tzal3x opened this issue Jan 3, 2024 · 0 comments
Open

Accounts with too many objects can reach rpc rate limit #127

Tzal3x opened this issue Jan 3, 2024 · 0 comments
Labels
enhancement New feature or request priority:low

Comments

@Tzal3x
Copy link
Collaborator

Tzal3x commented Jan 3, 2024

Reaching this rate limit results to failed transactions with a socket hang up error.

How many objects are "too many" depends on the rpc rate limit, but as a rule of thumb let's say anything greater than 500.

To resolve this we could either increase the amount of objects that are fetched lazily into the mainPool or load all the objects at once instead of batches.

@Tzal3x Tzal3x added enhancement New feature or request priority:low labels Jan 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request priority:low
Projects
None yet
Development

No branches or pull requests

1 participant