1,000,000 backtest simulations in 20 seconds with vectorbt

April 29, 2023
Facebook logo.
Twitter logo.
LinkedIn logo.

1,000,000 backtest simulations in 20 seconds with vectorbt

The first time I tried to backtest a pairs trading strategy, I used MATLAB.

I was excited when I ran the strategy and saw great results.

When I traded the strategy live, I lost money immediately.

So I ran backtest simulations to optimize the z-score and ADF test statistic.

I ran it again and had amazing results again!

And I lost money.


And again.

And again.

It turned out that I was making a big mistake.

One that costs countless traders countless money.

I was tweaking my parameters based on random fluctuations in the data, instead of real market inefficiencies.

I learned my lesson the only way traders do:

By losing money.

In 2023, there are dozens of backtesting frameworks.

But very few efficiently optimize parameters.

And fewer still let you efficiently optimize parameters the right way:

Using walk-forward optimization.

vectorbt is a new Python library that addresses that.

Here’s how.

1,000,000 backtest simulations in 20 seconds with vectorbt

vectorbt is a package that combines backtesting and data science.

It takes a “vectorized” approach to backtesting using pandas and NumPy.

This means that instead of looping through every day of data, it operates on all the data at once.

This allows for testing millions of strategies in a few seconds.

This is important when optimizing parameters, entry and exit types, and even the statistical significance of the strategy as a whole.

To avoid overfitting, pros use a technique called walk-forward optimization.

Walk-forward optimization is a technique used to find the best settings for a trading strategy.

Today, you’ll build a simple moving average crossover strategy. Then you’ll use walk-forward optimization to find the moving average windows that result in the best Sharpe ratio. Finally, you’ll test whether the out-of-sample results are statistically greater than the in-sample results.

Imports and set up

Start by importing NumPy and vectorbt. You’ll use SciPy to test the statistical significance of the results.

1import numpy as np
2import scipy.stats as stats
4import vectorbt as vbt

Then create an array of moving average windows to test and download price data.

1windows = np.arange(10, 50)
3price = vbt.YFData.download('AAPL').get('Close')

Build the functions

Create the data splits for the walk-forward optimization.

1(in_price, in_indexes), (out_price, out_indexes) = price.vbt.rolling_split(
2    n=30, 
3    window_len=365 * 2,
4    set_lens=(180,),
5    left_to_right=False,

This code segments the prices into 30 splits, each two years long, and reserves 180 days for the test.

Now create the functions that run the backtest.

1def simulate_all_params(price, windows, **kwargs):
2    fast_ma, slow_ma = vbt.MA.run_combs(
3        price, windows, r=2, short_names=["fast", "slow"]
4    )
5    entries = fast_ma.ma_crossed_above(slow_ma)
6    exits = fast_ma.ma_crossed_below(slow_ma)
8    pf = vbt.Portfolio.from_signals(price, entries, exits, **kwargs)
9    return pf.sharpe_ratio()

This function builds two moving averages for each window you pass in.

Then it creates DataFrames showing where the fast-moving average crosses above the slow-moving average. These are the trade entries. It does the opposite for the trade exits.

After the backtest is run, the function returns the Sharpe ratio.

Next, you need to figure out the combination of windows that maximizes the Sharpe ratio.

1def get_best_index(performance, higher_better=True):
2    if higher_better:
3        return performance[performance.groupby('split_idx').idxmax()].index
4    return performance[performance.groupby('split_idx').idxmin()].index
6def get_best_params(best_index, level_name):
7    return best_index.get_level_values(level_name).to_numpy()

The first function returns the indexes in the DataFrame for the windows in each data split that maximizes the Sharpe ratio. The second function returns the window values.

Finally, create a function that runs the backtest with the windows that maximize the Sharpe ratio.

1def simulate_best_params(price, best_fast_windows, best_slow_windows, **kwargs):
3    fast_ma = vbt.MA.run(price, window=best_fast_windows, per_column=True)
4    slow_ma = vbt.MA.run(price, window=best_slow_windows, per_column=True)
6    entries = fast_ma.ma_crossed_above(slow_ma)
7    exits = fast_ma.ma_crossed_below(slow_ma)
9    pf = vbt.Portfolio.from_signals(price, entries, exits, **kwargs)
10    return pf.sharpe_ratio()

This function creates the moving average values that maximize the Sharpe ratio, runs the backtest, and returns the Sharpe ratio.

Run the analysis

Start by optimizing the moving average windows on the in-sample data.

1in_sharpe = simulate_all_params(
2    in_price, 
3    windows, 
4    direction="both", 
5    freq="d"

The result is a DataFrame that has the Sharpe ratio for the best combination of windows for each split.

Now you can get the optimized windows and test them with out-of-sample data.

1in_best_index = get_best_index(in_sharpe)
3in_best_fast_windows = get_best_params(
4    in_best_index,
5    'fast_window'
7in_best_slow_windows = get_best_params(
8    in_best_index,
9    'slow_window'
11in_best_window_pairs = np.array(
12    list(
13        zip(
14            in_best_fast_windows, 
15            in_best_slow_windows
16        )
17    )

Running this code gives you the parameter values for the fast-moving average and slow-moving average you can test with the out-of-sample data.

1out_test_sharpe = simulate_best_params(
2    out_price, 
3    in_best_fast_windows, 
4    in_best_slow_windows, 
5    direction="both", 
6    freq="d"

The result is a DataFrame that has the Sharpe ratio for the backtest using out-of-sample test data and the window values that optimize the Sharpe ratio from the in-sample data.

Compare the results

The whole point of this analysis is to understand if the parameters you fit on the in-sample data can be used in real life to make money.

The most common issue in backtesting is overfitting to random data. (Especially when using technical analysis.)

You can run a simple t-test to understand if the out-of-sample Sharpe ratio is statistically greater than the in-sample Sharpe ratio. If it were, it would give you some measure of confidence that you did not overfit to random data.

1in_sample_best = in_sharpe[in_best_index].values
2out_sample_test = out_test_sharpe.values
4t, p = stats.ttest_ind(
5    a=out_sample_test,
6    b=in_sample_best,
7    alternative="greater"

In this case, the p-value is close to 1 which means you cannot reject the null hypothesis that the out-of-sample Sharpe ratios are greater than the in-sample Sharpe ratios.

In other words, you are overfitted to noise.

The moving crossover is a toy example that is known not to make money. But the technique of optimizing parameters using walk-forward optimization is the state-of-the-art way of removing as much bias as possible.

And vector bt is the state-of-the-art backtesting library that makes it possible.

Man with glasses and a wristwatch, wearing a white shirt, looking thoughtfully at a laptop with a data screen in the background.