Features
Performance
Scale computation with chunking, caching, JIT compilation, and parallel execution
✅ Most workflows that use the VBT's execution framework—such as data pulling, chunking, parameterization, splitting, and optimization—can now offload intermediate results to disk and reload them if the workflow crashes and restarts. You can confidently test billions of parameter combinations on cloud instances without worrying about losing your data.
np.random.seed(42)
@vbt.parameterized(cache_chunks=True, chunk_len=1)
def basic_iterator(i):
print("i:", i)
rand_number = np.random.uniform()
if rand_number < 0.2:
print("failed ⛔")
raise ValueError
return i
attempt = 0
while True:
attempt += 1
print("attempt", attempt)
try:
basic_iterator(vbt.Param(np.arange(10)))
print("completed 🎉")
break
except ValueError:
passattempt 1
i: 0
i: 1
i: 2
i: 3
i: 4
failed ⛔
attempt 2
i: 4
failed ⛔
attempt 3
i: 4
failed ⛔
attempt 4
i: 4
i: 5
i: 6
i: 7
failed ⛔
attempt 5
i: 7
i: 8
i: 9
completed 🎉✅ Most rolling indicators implemented with Pandas and NumPy require multiple passes over the data. For example, calculating the sum of three arrays requires at least two passes. If you want to calculate such an indicator iteratively (bar by bar), you either need to pre-calculate everything and store it in memory or re-calculate each window, which can significantly impact performance. Accumulators, however, maintain an internal state that allows you to compute an indicator value as soon as a new data point arrives, resulting in the best possible performance.
@njit
def fastest_rolling_zscore_1d_nb(arr, window, minp=None, ddof=1):
if minp is None:
minp = window
out = np.full(arr.shape, np.nan)
cumsum = 0.0
cumsum_sq = 0.0
nancnt = 0
for i in range(len(arr)):
pre_window_value = arr[i - window] if i - window >= 0 else np.nan
mean_in_state = vbt.nb.RollMeanAIS(
i, arr[i], pre_window_value, cumsum, nancnt, window, minp
)
mean_out_state = vbt.nb.rolling_mean_acc_nb(mean_in_state)
_, _, _, mean = mean_out_state
std_in_state = vbt.nb.RollStdAIS(
i, arr[i], pre_window_value, cumsum, cumsum_sq, nancnt, window, minp, ddof
)
std_out_state = vbt.nb.rolling_std_acc_nb(std_in_state)
cumsum, cumsum_sq, nancnt, _, std = std_out_state
out[i] = (arr[i] - mean) / std
return out
data = vbt.YFData.pull("BTC-USD")
rolling_zscore = fastest_rolling_zscore_1d_nb(data.returns.values, 14)
data.symbol_wrapper.wrap(rolling_zscore)Date
2014-09-17 00:00:00+00:00 NaN
2014-09-18 00:00:00+00:00 NaN
2014-09-19 00:00:00+00:00 NaN
...
2023-02-01 00:00:00+00:00 0.582381
2023-02-02 00:00:00+00:00 -0.705441
2023-02-03 00:00:00+00:00 -0.217880
Freq: D, Name: BTC-USD, Length: 3062, dtype: float64(data.returns - data.returns.rolling(14).mean()) / data.returns.rolling(14).std()Date
2014-09-17 00:00:00+00:00 NaN
2014-09-18 00:00:00+00:00 NaN
2014-09-19 00:00:00+00:00 NaN
...
2023-02-01 00:00:00+00:00 0.582381
2023-02-02 00:00:00+00:00 -0.705441
2023-02-03 00:00:00+00:00 -0.217880
Freq: D, Name: Close, Length: 3062, dtype: float64✅ A new, innovative chunking mechanism lets you specify how arguments should be chunked. It automatically splits array-like arguments, passes each chunk to the function for execution, and then merges the results. This enables you to split large arrays and run any function in a distributed manner. VBT also features a central registry and provides chunking specifications for all arguments of most Numba-compiled functions, including simulation functions. Chunking can be enabled with a single command. You no longer have to worry about out-of-memory errors! 🎉
@vbt.chunked(
chunk_len=100,
merge_func="concat",
execute_kwargs=dict(
clear_cache=True,
collect_garbage=True
)
)
def backtest(data, fast_windows, slow_windows):
fast_ma = vbt.MA.run(data.close, fast_windows, short_name="fast")
slow_ma = vbt.MA.run(data.close, slow_windows, short_name="slow")
entries = fast_ma.ma_crossed_above(slow_ma)
exits = fast_ma.ma_crossed_below(slow_ma)
pf = vbt.PF.from_signals(data.close, entries, exits)
return pf.total_return
param_product = vbt.combine_params(
dict(
fast_window=vbt.Param(range(2, 100), condition="fast_window < slow_window"),
slow_window=vbt.Param(range(2, 100)),
),
build_index=False
)
backtest(
vbt.YFData.pull(["BTC-USD", "ETH-USD"]),
vbt.Chunked(param_product["fast_window"]),
vbt.Chunked(param_product["slow_window"])
)fast_window slow_window symbol
2 3 BTC-USD 193.124482
ETH-USD 12.247315
4 BTC-USD 159.600953
ETH-USD 15.825041
5 BTC-USD 124.703676
...
97 98 ETH-USD 3.947346
99 BTC-USD 25.551881
ETH-USD 3.442949
98 99 BTC-USD 27.943574
ETH-USD 3.540720
Name: total_return, Length: 9506, dtype: float64✅ Most Numba-compiled functions have been rewritten to process columns in parallel using
automatic parallelization with @jit.
You can enable this with a single command. This approach is best for lightweight functions that are
applied to wide arrays.
np.random.seed(42)
df = pd.DataFrame(np.random.uniform(size=(1000, 1000)))
%timeit df.rolling(10).mean() 45.6 ms ± 138 µs per loop (mean ± std. dev. of 7 runs, 10 loops each)%timeit df.vbt.rolling_mean(10) 5.33 ms ± 302 µs per loop (mean ± std. dev. of 7 runs, 1 loop each)%timeit df.vbt.rolling_mean(10, jitted=dict(parallel=True)) 1.82 ms ± 5.21 µs per loop (mean ± std. dev. of 7 runs, 1000 loops each)✅ Integration of ThreadPoolExecutor
from concurrent.futures, ThreadPool
from pathos, and Dask backend for running multiple chunks across multiple
threads. This is best for speeding up heavyweight functions that release the GIL, such as Numba and C
functions. Multithreading + Chunking + Numba = 💪
data = vbt.YFData.pull(["BTC-USD", "ETH-USD"])
%timeit vbt.PF.from_random_signals(data.close, n=[100] * 1000, seed=42)613 ms ± 37.2 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)%timeit vbt.PF.from_random_signals(data.close, n=[100] * 1000, seed=42, chunked="threadpool")294 ms ± 8.91 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)✅ Integration of ProcessPoolExecutor
from concurrent.futures, ProcessPool
and ParallelPool from
pathos, WorkerPool from
mpire, and Ray backend for running multiple chunks across multiple processes.
This is best for speeding up heavyweight functions that do not release the GIL, such as regular Python
functions, as well as lightweight arguments that are easy to serialize. Ever wanted to test billions of
hyperparameter combinations in just a few minutes? Now you can by scaling functions and entire
applications in the cloud using Ray clusters
👀
@vbt.chunked(
size=vbt.ArraySizer(arg_query="items", axis=1),
arg_take_spec=dict(
items=vbt.ArraySelector(axis=1)
),
merge_func=np.column_stack
)
def bubble_sort(items):
items = items.copy()
for i in range(len(items)):
for j in range(len(items) - 1 - i):
if items[j] > items[j + 1]:
items[j], items[j + 1] = items[j + 1], items[j]
return items
np.random.seed(42)
items = np.random.uniform(size=(1000, 3))
%timeit bubble_sort(items)456 ms ± 1.36 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)%timeit bubble_sort(items, _execute_kwargs=dict(engine="pathos"))165 ms ± 1.51 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)✅ Jitting stands for just-in-time compiling. In the VBT universe, however, jitting simply means accelerating. While Numba remains the primary jitter, VBT now allows you to implement custom jitter classes, such as those for vectorized NumPy or even JAX with GPU support. Every jitted function is registered globally, so you can switch between different implementations or even disable jitting entirely with a single command.
data = vbt.YFData.pull("BTC-USD", start="7 days ago")
log_returns = np.log1p(data.close.pct_change())
log_returns.vbt.cumsum() Date
2023-01-31 00:00:00+00:00 0.000000
2023-02-01 00:00:00+00:00 0.024946
2023-02-02 00:00:00+00:00 0.014271
2023-02-03 00:00:00+00:00 0.013310
2023-02-04 00:00:00+00:00 0.008288
2023-02-05 00:00:00+00:00 -0.007967
2023-02-06 00:00:00+00:00 -0.010087
Freq: D, Name: Close, dtype: float64log_returns.vbt.cumsum(jitted=False) Date
2023-01-31 00:00:00+00:00 0.000000
2023-02-01 00:00:00+00:00 0.024946
2023-02-02 00:00:00+00:00 0.014271
2023-02-03 00:00:00+00:00 0.013310
2023-02-04 00:00:00+00:00 0.008288
2023-02-05 00:00:00+00:00 -0.007967
2023-02-06 00:00:00+00:00 -0.010087
Freq: D, Name: Close, dtype: float64@vbt.register_jitted(task_id_or_func=vbt.nb.nancumsum_nb)
def nancumsum_np(arr):
return np.nancumsum(arr, axis=0)
log_returns.vbt.cumsum(jitted="np") Date
2023-01-31 00:00:00+00:00 0.000000
2023-02-01 00:00:00+00:00 0.024946
2023-02-02 00:00:00+00:00 0.014271
2023-02-03 00:00:00+00:00 0.013310
2023-02-04 00:00:00+00:00 0.008288
2023-02-05 00:00:00+00:00 -0.007967
2023-02-06 00:00:00+00:00 -0.010087
Freq: D, Name: Close, dtype: float64✅ Caching has been completely reimplemented and is now managed by a central registry. This enables tracking useful statistics for all cacheable parts of VBT, such as showing the total cached size in MB. You get full control and transparency 🪟
data = vbt.YFData.pull("BTC-USD")
pf = vbt.PF.from_random_signals(data.close, n=5, seed=42)
_ = pf.stats()
pf.get_ca_setup().get_status_overview(
filter_func=lambda setup: setup.caching_enabled,
include=["hits", "misses", "total_size"]
) hits misses total_size
object
portfolio:0.drawdowns 0 1 70.9 kB
portfolio:0.exit_trades 0 1 70.5 kB
portfolio:0.filled_close 6 1 24.3 kB
portfolio:0.init_cash 3 1 32 Bytes
portfolio:0.init_position 0 1 32 Bytes
portfolio:0.init_position_value 0 1 32 Bytes
portfolio:0.init_value 5 1 32 Bytes
portfolio:0.input_value 1 1 32 Bytes
portfolio:0.orders 9 1 69.7 kB
portfolio:0.total_profit 1 1 32 Bytes
portfolio:0.trades 0 1 70.5 kB✅ Rolling metrics based on returns have been optimized for maximum performance—up to 1000x speedup!
import quantstats as qs
index = vbt.date_range("2020", periods=100000, freq="1min")
np.random.seed(42)
returns = pd.Series(np.random.normal(0, 0.001, size=len(index)), index=index)
%timeit qs.stats.rolling_sortino(returns, rolling_period=10) 2.79 s ± 24.8 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)%timeit returns.vbt.returns.rolling_sortino_ratio(window=10) 8.12 ms ± 199 µs per loop (mean ± std. dev. of 7 runs, 1 loop each)And many more...
⏩ Look forward to more killer features being added every release!
Copyright © 2021–2026 Oleg Polakow. All rights reserved.
Site content and documentation are provided for using and evaluating VectorBT PRO and for educational purposes. Any other use, including building or supporting competing products or services, requires prior written consent.