-
Notifications
You must be signed in to change notification settings - Fork 102
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
Docker - Connection aborted #177
Comments
also why is |
more errors keep coming...
|
OK more on the same error.... and eventually (after 45 minutes or so) janopicus dies:
Full console dump:
|
Hey, it seems that each backtest is taking too long, so long that the connection dies before the result is ready. Taking 45 minutes to run this very few backtests just add weight to this hypothesis. I have never seen this, the normal thing here is each backtest taking 5 seconds at max. So, many things could lead to this: is your strategy particularly heavy on computing? Is your CPU 4-core at least? How long it takes to run a similar backtest on gekko alone, outside docker? |
Ah... ok I'm using a MacBook (Retina, 12-inch, 2017) so yeah 4 cores. I am testing the NEO strategy. snippet from my current console:
|
hey, so that's really it, taking too long to backtest. Your rig seems suitable, so maybe it is CPU throttled for power saving or docker is impairing performance. 50s per backtest is still too much, you won't be able to get useful results at this rate even if it is working... |
OK so I have Japonicus finally up and running using Docker (and I have absolutely no idea how to use Japonicus yet, but this is where the fun starts...)
The gekko/japonicus combo has been running for about an hour and now I am getting this below. Also the Gekko web interface is terribly slow.
Could it be that japonicus is simply overloading my poor little gekko bot?
The text was updated successfully, but these errors were encountered: