A written reference on freqtrade backtesting engine — how it works, how to configure it, and where it breaks under load.
How It Works
freqtrade backtesting engine operates as a pipeline: ingest, compute, decide, route. Each stage has its own ways to break.
Configuration
Configuring freqtrade backtesting engine comes down to a handful of parameters. Vendor defaults suit demos; production deserves its own tuning pass.
Failure Modes
freqtrade backtesting engine breaks in recognizable ways: silent data gaps, parameters that stopped matching the market, and latency spikes at the worst moment.
Evaluation
Judge freqtrade backtesting engine on measured outcomes — distribution of returns, drawdown depth, operational burden — not on a single lucky stretch.
Configuration Reference
# Freqtrade Backtesting Engine tested configuration mode: production timeframe: auto risk_limits: max_drawdown: 15 percent max_position: 3 percent monitoring: alert_threshold: 0.5 report_interval: hourly
Parameter Impact
| Parameter | Effect | Trade-off |
|---|---|---|
| timeframe | Signal frequency | Higher means fewer but more reliable signals |
| risk_limit | Maximum exposure | Lower means safer but slower returns |
| lookback | Indicator sensitivity | Longer means smoother but lagging |