-
Notifications
You must be signed in to change notification settings - Fork 18
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
Performance problem it takes 525448.93998 ms to finish #37
Comments
Switching to sockets is a great idea! Will see what their api offers on that connection. |
What do you mean "dust” , the trade remaining ? Or unprofitable coins ? Btw i created slack channel and invited you if you wish for better communication , brainstorming, etc |
Thanks for the invite, joined! Dust are all assets that are in your portfolio but only worth a few bucks. Like 0.24$ of Digibyte. |
Regrading to Dust Coins issue , |
Performance:
This comes due to the limitation of the bittrex api. It only allows ~60requests per minute. So we have some manual wait time between requests to not get blocked.
Sadly this results in the long total amount. We could see which requests we can omit to speed things up. But for now I don't know which.
Stopping buying new coins:
Maybe there isn't any viable option for buying currently? Adding those shouldn't general break the evaluation of other options.
I'll improve the logging to reflect this behavior. Would you mind opening an issue for that?
Originally posted by @saschb2b in #33 (reply in thread)
https://bittrex.github.io/api/v3
The text was updated successfully, but these errors were encountered: