Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Networking and requests #1

Open
emirhanyasin opened this issue May 10, 2021 · 0 comments
Open

Networking and requests #1

emirhanyasin opened this issue May 10, 2021 · 0 comments

Comments

@emirhanyasin
Copy link

I could not understand what you mean by,
"Thanks to this tuning, instead of having our worker being limited to 5 req/sec, we can have 20 req/sec, and we could theoritically scale this limit to 3,750 req/sec with a c5d.18xlarge.

This parameter is important, since the first strategy implemented is an arbitrage using 3 quotes on one exchange (ex: BTC→ETH, ETH→TRX, TRX→BTC). By fetching the 3 quotes 6 times per seconds, we are more reactive than the users getting the quotes using the websocket API."

What limits the worker to 5req/sec and how you made it to 20?
What do you mean here by being more reactive than the users getting the quotes using websocket?

I will be very happy if you can explain them.

Regards,
Emirhan

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant