⚡ Vectorize Black-Scholes pricing for butterfly arbitrage detection#9
Conversation
…pricing Co-authored-by: sharesth23 <182501306+sharesth23@users.noreply.github.com>
|
👋 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 New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
💡 What: Vectorized the
bs_call_pricefunction usingnumpy.whereto handle scalar and array inputs efficiently, and updatedbutterfly_arbitrageto leverage this vectorization instead of using a list comprehension loop.🎯 Why: To improve performance by minimizing Python loop overhead and taking advantage of highly optimized C operations in NumPy for large arrays of strikes and implied volatilities.
📊 Measured Improvement: The
butterfly_arbitragefunction benchmark exhibited a runtime decrease from ~1.724 seconds to ~0.024 seconds representing roughly a 71x performance improvement.PR created automatically by Jules for task 17826642749449070650 started by @sharesth23