03-26-2018, 01:13 PM
(This post was last modified: 03-26-2018, 02:58 PM by tommiehansen.
Edit Reason: Post written on tablet, looked like shit -- rewrite
)
One of the problems i personally got (and maybe other 3rd party tools) is that killGekko() currently requires ID's. One can understand why one would create it like so but it's makes it much harder to e.g. kill all running backtests or all running imports.
This is not a problem for when e.g. running small backtests taking 5-15 seconds, but imagine multithreading runs that on average take 5-30 minutes to complete...
The only way to "fix" wanting to stop e.g. 3x of such runs is to force kill the entire Gekko service which is less then ideal since it isn't certain that the user actually got access to the terminal (could be using Gekko instance as a remote service etc).
Wishlist
1. Add categories to killGekko so that it accepts e.g. 'backtest' or 'import' and not only specific ID's.
2. Any categorical "kill" event simply kills all running X within a category e.g. killGekko({ category: 'backtest' }) would kill all running backtests.
3. Major kill-switch; killGekko({ category: 'all' })
This is not a problem for when e.g. running small backtests taking 5-15 seconds, but imagine multithreading runs that on average take 5-30 minutes to complete...
The only way to "fix" wanting to stop e.g. 3x of such runs is to force kill the entire Gekko service which is less then ideal since it isn't certain that the user actually got access to the terminal (could be using Gekko instance as a remote service etc).
Wishlist
1. Add categories to killGekko so that it accepts e.g. 'backtest' or 'import' and not only specific ID's.
2. Any categorical "kill" event simply kills all running X within a category e.g. killGekko({ category: 'backtest' }) would kill all running backtests.
3. Major kill-switch; killGekko({ category: 'all' })