Closed l3104468710 closed 1 month ago
Seems like the usual "run out of memory" issue
seems like it, yes - but "the usual error" won't help a user who never encountered this :laughing:
Best try to reduce the timerange for your backtest to counter this.
Depending on the timeframe (and number of pairs) - memory consumption can become significant - and at some point, the operating systems ofte decide to "victimze" the process with the most memory consumption. The process (freqtrade, in this case) will not be informed by this - so there's no way for us to show a message highlighting this.
The combination of "docker on windows" makes this slightly worse - as by default, docker will not be able to use all available memory - but is limited to 2GB of the host's memory source. Apparently, this can be increased in the UI - though i've never tried this combination myself.
using --eps
will make this problem worse - and will result in a backtest that is impossible to reproduce (this setting serves a very specific purpose - and is not suited / meant for regular use).
Closing this - as it's a "simple" out of memory error - to which solutions have been described above.
Describe your environment
Your question
Strategy backtesting without error alerts, auto-stop
This is backtesting command: docker compose run --rm freqtrade backtesting -s VWAP --timerange 20220101- --dry-run-wallet 10000 --stake-amount 1000 --eps --breakdown month
This is part of the running log: 2024-05-08 12:03:55,698 - freqtrade.data.history.datahandlers.idatahandler - WARNING - XRP/USDT:USDT, funding_rate, 8h, data starts at 2022-01-01 00:00:00 2024-05-08 12:03:55,720 - freqtrade.data.history.datahandlers.idatahandler - WARNING - YFI/USDT:USDT, funding_rate, 8h, data starts at 2022-01-01 00:00:00 2024-05-08 12:03:55,742 - freqtrade.data.history.datahandlers.idatahandler - WARNING - ZEN/USDT:USDT, funding_rate, 8h, data starts at 2022-01-01 00:00:00 2024-05-08 12:03:55,887 - freqtrade.data.history.datahandlers.idatahandler - WARNING - APE/USDT:USDT, mark, 8h, data starts at 2022-03-17 08:00:00 2024-05-08 12:03:55,909 - freqtrade.data.history.datahandlers.idatahandler - WARNING - API3/USDT:USDT, mark, 8h, data starts at 2022-02-21 08:00:00 2024-05-08 12:03:56,273 - freqtrade.data.history.datahandlers.idatahandler - WARNING - DUSK/USDT:USDT, mark, 8h, data starts at 2022-01-06 08:00:00 2024-05-08 12:03:56,487 - freqtrade.data.history.datahandlers.idatahandler - WARNING - FLOW/USDT:USDT, mark, 8h, data starts at 2022-02-09 08:00:00 2024-05-08 12:03:56,606 - freqtrade.data.history.datahandlers.idatahandler - WARNING - JASMY/USDT:USDT, mark, 8h, data starts at 2022-04-19 00:00:00 2024-05-08 12:03:56,848 - freqtrade.data.history.datahandlers.idatahandler - WARNING - OP/USDT:USDT, mark, 8h, data starts at 2022-06-01 00:00:00 2024-05-08 12:03:57,293 - freqtrade.optimize.backtesting - INFO - Dataload complete. Calculating indicators 2024-05-08 12:03:57,296 - freqtrade.optimize.backtesting - WARNING - Backtest result caching disabled due to use of open-ended timerange. 2024-05-08 12:03:57,296 - freqtrade.optimize.backtesting - INFO - Running backtesting for Strategy VWAP 2024-05-08 12:03:57,297 - freqtrade.strategy.hyper - INFO - No params for buy found, using default values. 2024-05-08 12:03:57,297 - freqtrade.strategy.hyper - INFO - No params for sell found, using default values. 2024-05-08 12:03:57,297 - freqtrade.strategy.hyper - INFO - No params for protection found, using default values. 2024-05-08 12:07:29,825 - freqtrade.optimize.backtesting - INFO - Backtesting with data from 2022-01-01 00:00:00 up to 2024-05-07 13:25:00 (857 days).
E:\ft_userdata\user_data>
This is my strategy code:
Ask the question you have not been able to find an answer in the Documentation