Skip to content
This repository has been archived by the owner on Oct 30, 2023. It is now read-only.

Stop working after snapshot #3

Closed
liho98 opened this issue Jan 1, 2021 · 4 comments
Closed

Stop working after snapshot #3

liho98 opened this issue Jan 1, 2021 · 4 comments
Labels
good first issue Good for newcomers

Comments

@liho98
Copy link

liho98 commented Jan 1, 2021

image

Trader is not operating, Im installed latest Rust and running on Ubuntu vm, but no orders are placed. Could you check on this when youre free.

Telegram also enabled, but I did not received any notifications as well.

@gabriel-milan
Copy link
Owner

Hi there, thank you for getting in touch! Actually, the trader is operating as expected, but it will only print out when it finds a transaction that's worth it, according to your configuration file. Telegram notifications also work this way, you'll get them as soon as a trade is performed. If you want to debug that, disable trading on your configuration file and set profit threshold to negative 100% and age threshold to something high, like 200ms.

@liho98
Copy link
Author

liho98 commented Jan 1, 2021

Hi there, thank you for getting in touch! Actually, the trader is operating as expected, but it will only print out when it finds a transaction that's worth it, according to your configuration file. Telegram notifications also work this way, you'll get them as soon as a trade is performed. If you want to debug that, disable trading on your configuration file and set profit threshold to negative 100% and age threshold to something high, like 200ms.

My inventment_base is "USDT"

I running for an hour but did not even found an arbitrage opportunity... Meaning, its very difficult to arbitrage in binance right?

Besides, this bot is cpu intensive, my vm spec is 1vcpu 2gb ram, and it took 100% of the cpu while its running. Izit I need to upgrade to 2vcpu? or higher

@gabriel-milan
Copy link
Owner

its very difficult to arbitrage in binance right?

That's probably accurate. Your configuration will filter transactions. The more aggressive you're with that, the less arbitrage deals will show up.

this bot is cpu intensive

Just think about it: you're handling 757 web sockets, continuously streaming data every 100ms to the bot. It has to handle this information ASAP and also compute profit for all those 558 triangular relationships (thousands of times every second if you want it to attend your age threshold parameter). It's gotta be intensive, right? You can probably run that with 1 vCPU, but that means it's going to take longer to compute stuff, resulting in the age parameter being really high. Arbitrage deals need to be computed within a few milliseconds. Does it feel expensive?

@liho98
Copy link
Author

liho98 commented Jan 1, 2021

its very difficult to arbitrage in binance right?

That's probably accurate. Your configuration will filter transactions. The more aggressive you're with that, the less arbitrage deals will show up.

this bot is cpu intensive

Just think about it: you're handling 757 web sockets, continuously streaming data every 100ms to the bot. It has to handle this information ASAP and also compute profit for all those 558 triangular relationships (thousands of times every second if you want it to attend your age threshold parameter). It's gotta be intensive, right? You can probably run that with 1 vCPU, but that means it's going to take longer to compute stuff, resulting in the age parameter being really high. Arbitrage deals need to be computed within a few milliseconds. Does it feel expensive?

Yeah sound like quite expensive, I think i will try to upgrade to 2vcpu. Thanks for the great work, and your explanation!

@liho98 liho98 closed this as completed Jan 1, 2021
@gabriel-milan gabriel-milan added the good first issue Good for newcomers label Jan 1, 2021
@gabriel-milan gabriel-milan pinned this issue Jan 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants