too shallow to convert

[numairawan]

I am trying to run it but keeps getting this error, I also increase the depth to 1000 and add the "USDT","CAKE","ONE","ETC","BTC","BUSD","BNB" in the whitelist but same error in performence.log.

I am using USDT as base coin.

[bmino]

Please post the full error message. I am assuming you get: ... depth (0) too shallow to convert ...

which typically means your cpu is being overwhelmed and the websockets are timing out

[sergeykhliustin]

Hi! I want to note the same issue, sockets always timeout and disconnecting. But when looking on htop command, seems like one core is around 100%, but others are not busy (8 cpu total)

[bmino]

Yup, this isn't utilizing multiple threads so your cpu usage might say 10% usage, but one of your 8 threads is maxed out performing calculations. The app logging is watching for clock time being eaten up for calculations and will now warn you when this is too high at every status update interval

[k4m4h4l]

[3/4/2021, 12:00:51 PM] DEBUG: Depth cache updates per second: 850.90 [3/4/2021, 12:00:51 PM] DEBUG: CPU clock usage for calculations: 35.27% [3/4/2021, 12:00:51 PM] DEBUG: API Latency: 255 ms

only 32% Usage

I have the same problem what would be a solution to fix

[bmino]

I originally saw disconnects as that number passed 50% but issues might present themselves earlier. You can reduce the cpu intensity by decreasing INVESTMENT.STEP or INVESTMENT.MAX and other options like depth will affect this @k4m4h4l