Charted notes on freqtrade backtesting engine in trading automation: mechanics, waypoints, and the wrecks recorded in production.
Mechanics
The mechanics of freqtrade backtesting engine form one pipeline: raw market data in, computed signal out, decision routed to the order engine.
Waypoints (Configuration)
Configuring freqtrade backtesting engine comes down to a short list of parameters. Vendor defaults fit demonstrations; live deployment deserves its own pass.
Wreck Record (Failure Modes)
freqtrade backtesting engine sinks in recognizable ways: silent feed gaps, parameters no longer matching the market, latency spikes at the worst moment.
Navigation Checks (Evaluation)
An honest assessment of freqtrade backtesting engine weighs quantitative metrics beside code quality and the attention it demands in production.
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 |