Skip to content

⚡ Bolt: Replace O(n) array filtering with O(log n) binary search in backtest loop and data clipping#45

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

⚡ Bolt: Replace O(n) array filtering with O(log n) binary search in backtest loop and data clipping#45
toreleon wants to merge 1 commit into
masterfrom
bolt-binary-search-opt-7586609244798221536

Conversation

@toreleon

Copy link
Copy Markdown
Owner

⚡ Bolt: Replace O(n) array filtering with O(log n) binary search in backtest loop and data clipping

💡 What:
Replaced the Array.prototype.filter() operations with an O(log n) binary search (findLastBarIndex) inside the backtest data loops (priceOverride, vnindexAt) and historical data clipping (clipBars).

🎯 Why:
The time-series arrays for bars and vnindex are inherently sorted chronologically. Running an O(n) scan via .filter() per interval per ticker during a backtest causes an unnecessary O(t * i * n) iteration bottleneck.

📊 Impact:
Massive reduction in time complexity (O(n) to O(log n)) per lookup within the critical path of the backtest runner loop.

🔬 Measurement:
Run the Vitest suite or execute a /backtest in the CLI to observe equivalent behavior with a theoretically more performant data resolution.


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

…acktest loop and data clipping

💡 What:
Replaced the `Array.prototype.filter()` operations with an `O(log n)` binary search (`findLastBarIndex`) inside the backtest data loops (`priceOverride`, `vnindexAt`) and historical data clipping (`clipBars`).

🎯 Why:
The time-series arrays for `bars` and `vnindex` are inherently sorted chronologically. Running an `O(n)` scan via `.filter()` per interval per ticker during a backtest causes an unnecessary `O(t * i * n)` iteration bottleneck.

📊 Impact:
Massive reduction in time complexity (`O(n)` to `O(log n)`) per lookup within the critical path of the backtest runner loop.

🔬 Measurement:
Run the Vitest suite or execute a `/backtest` in the CLI to observe equivalent behavior with a theoretically more performant data resolution.

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