Skip to content

⚡ Bolt: Use binary search for timeseries lookups in backtesting#43

Draft
toreleon wants to merge 1 commit into
masterfrom
bolt-binary-search-opt-12546536491596426527
Draft

⚡ Bolt: Use binary search for timeseries lookups in backtesting#43
toreleon wants to merge 1 commit into
masterfrom
bolt-binary-search-opt-12546536491596426527

Conversation

@toreleon

Copy link
Copy Markdown
Owner

💡 What: Replaced an O(n) array .filter() inside the backtest interval loop with an O(log n) binary search utility findPriceAt for retrieving the latest price asOf a timestamp.
🎯 Why: Backtests loop through thousands of intervals. Filtering an entire timeseries array every interval creates a severe O(n*m) performance bottleneck on the critical path.
📊 Impact: Expected to reduce lookup time from O(n) to O(log n), making overall backtest sessions significantly faster, especially over longer time frames or larger symbol universes.
🔬 Measurement: Run a large backtest before and after to observe runtime difference, or run an isolated script benchmarking .filter() vs binary search on an array of 10,000 dates (shows a multi-hundredfold improvement in lookups).


PR created automatically by Jules for task 12546536491596426527 started by @toreleon

💡 What: Replaced an O(n) array `.filter()` inside the backtest interval loop with an O(log n) binary search utility `findPriceAt` for retrieving the latest price `asOf` a timestamp.
🎯 Why: Backtests loop through thousands of intervals. Filtering an entire timeseries array every interval creates a severe O(n*m) performance bottleneck on the critical path.
📊 Impact: Expected to reduce lookup time from O(n) to O(log n), making overall backtest sessions significantly faster, especially over longer time frames or larger symbol universes.
🔬 Measurement: Run a large backtest before and after to observe runtime difference, or run an isolated script benchmarking `.filter()` vs binary search on an array of 10,000 dates (shows a multi-hundredfold improvement in lookups).

Co-authored-by: toreleon <42534763+toreleon@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant