Skip to content

⚡ Optimize simulate_trading performance (~250x speedup) - #254

Open
EiJackGH wants to merge 1 commit into
mainfrom
perf-trading-simulation-itertuples-7027114449770727939
Open

⚡ Optimize simulate_trading performance (~250x speedup)#254
EiJackGH wants to merge 1 commit into
mainfrom
perf-trading-simulation-itertuples-7027114449770727939

Conversation

@EiJackGH

@EiJackGH EiJackGH commented Aug 2, 2026

Copy link
Copy Markdown
Owner

💡 What: Replaced the pandas iterrows() loop in simulate_trading with itertuples() and updated state tracking to use pure Python variables (cash_val, btc_val) and lists. The final DataFrame is now constructed in bulk at the end of the simulation instead of modifying a DataFrame via .loc inside the loop.

🎯 Why: The existing approach using iterrows() combined with index-based assignment via portfolio.loc[i, 'cash'] inside a Python for-loop is notoriously slow in pandas. This approach triggered thousands of internal Series/DataFrame re-indexings and object creations, making large backtests painfully slow.

📊 Measured Improvement:
I established a benchmark simulating 10,000 trading days (approx. 27 years).

  • Baseline (iterrows()): ~8.62 seconds
  • Optimized (itertuples()): ~0.034 seconds
  • Result: A ~252x speedup on the core trading logic loop. Both approaches produce identical outputs (verified by assertions and tests).

PR created automatically by Jules for task 7027114449770727939 started by @EiJackGH

Replace the slow `iterrows()` loop and DataFrame `.loc` updates in the
`simulate_trading` function with `itertuples()` and state variables.
This fully removes Pandas overhead within the daily simulation loop.

Co-authored-by: EiJackGH <172181576+EiJackGH@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