Slow down polling on API rate limit errors #510

Open
opened 2022-06-28 00:10:01 -07:00 by scionaltera · 0 comments
scionaltera commented 2022-06-28 00:10:01 -07:00 (Migrated from github.com)

All exchanges have some kind of rate limit on how frequently you can call their APIs. They all start to throw some kind of exception if you exceed that limit, and some will blacklist your IP temporarily (or permanently if you don't stop). Right now these errors can create a lot of noise in the logs and we don't do anything to stop it from happening.

It would be smart if Arbitrader detected these rate limiting errors and slowed down polling for that exchange to try to avoid triggering them continuously. Best would be if it slowed down a little bit at first, but retained some sort of counter so it could manage the delay and find the fastest rate to poll without triggering the errors.

All exchanges have some kind of rate limit on how frequently you can call their APIs. They all start to throw some kind of exception if you exceed that limit, and some will blacklist your IP temporarily (or permanently if you don't stop). Right now these errors can create a lot of noise in the logs and we don't do anything to stop it from happening. It would be smart if Arbitrader detected these rate limiting errors and slowed down polling for that exchange to try to avoid triggering them continuously. Best would be if it slowed down a little bit at first, but retained some sort of counter so it could manage the delay and find the fastest rate to poll without triggering the errors.
Commenting is not possible because the repository is archived.
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
scion/arbitrader#510
No description provided.