Krypto-trading-bot: Incredibly high CPU utilizations driving >1000ms latencies

[halessi]

Hey,

I think the latest upgrade has worsened my CPU utilization problems -- this morning K has been absolutely maxing out two separate cores, leading to latencies of up to 1500ms (typically
~20ms). I'm on BTC/USD, with market levels set to 321|321. I've tried with database=:memory: and without.

The behavior is sporadic: it will drop to 100% then back up to 200% (full two cores). I can tell in the UI when it's maxing out, as this is when the latencies spike (computational backlog somehow?).

How can I downgrade to the previous commit? Or do you have any further ideas on troubleshooting? I can swap to ETH/USD or other pairs and see if the problem persists.

Thanks.

[ctubio]

sorry what exchange are you using?

:koala: thanks for the report'''

[halessi]

Thanks for the quick reply! using coinbase.

[ctubio]

umf, for me was all nice with coinbase; let me try to debug a bit before consider a rollback

any other info you may have will be very welcome¡' (to allow me to reproduce your very same situation)

:koala: quick link to previous version: https://github.com/ctubio/Krypto-trading-bot/releases/download/0.4.x/K-0.4.13.46-linux-x86_64.tar.gz (in case you preffer to revert; replace the binary at /usr/local/bin/K-trading-bot with the one found in the zip build-linux-x86_64/local/bin/K-trading-bot)

[halessi]

My K.sh file has pretty much everything standard (api key, secret, passphrase, exchange) with OPTIONAL_ARGUMENTS="
--database=:memory:
--maker-fee=0.15
--taker-fee=0.25"

Thanks for the link, I'll keep toying around and see if I can troubleshoot anything before reverting.

[ctubio]

i can notice some high cpu too; let me try a fix or otherwise i will rollback the release meanwhile fixing locally

many thanks for the quick report''' and sorry for the trouble''

[halessi]

no worries! i'm happy it wasn't just me. thanks for your quick working to fix it!!

[ctubio]

is suposed now that the cpu should be around 2% with max spikes of 6%; but feel free to comment in case you still have some offensive values.

meanwhile allow me to close the issue and turn the bug of today as a improvement for tomorrow; on next days i will try to go a bit lower without increasing latency; as is now latency is niiiice :D but cpu is still a liiiil high (1~3%) compared to previous commits

:koala: thanks for your (cpu) time'''

[halessi]

this worked! my cpu utilization is lower than it has ever been. thank you.