⚡ Bolt: Memoize blueprint variant API queries to resolve N+1 bottleneck#85
⚡ Bolt: Memoize blueprint variant API queries to resolve N+1 bottleneck#85merg357 wants to merge 1 commit into
Conversation
Co-authored-by: merg357 <221854052+merg357@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: Added
@functools.lru_cache(maxsize=None)toget_blueprint_variants()inmerg_bridge.pyand changed its return type to an immutabletuple.🎯 Why: Fixes an N+1 network bottleneck where the same blueprint provider's variants were repeatedly fetched from the Printify API during iterative bulk product creation loops.
📊 Impact: Eliminates redundant network requests, significantly reducing API latency and preventing potential rate limit errors when creating multiple products from the same blueprint.
🔬 Measurement: Time the execution of bulk product creation before and after the change; monitor API request logs to confirm the variant endpoint is only hit once per blueprint provider.
PR created automatically by Jules for task 9598767539003711653 started by @merg357