You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: