⚡ Bolt: Memoize Printify variant API queries#66
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_variantsinprintify_manager.py,create_merch.py, andmerch_factory.pyto memoize the Printify API responses. Changed the return type to an immutabletuple[int, ...]to guarantee thread-safety.🎯 Why: Iterative product creation loops repeatedly query the identical blueprint and print provider IDs, causing an N+1 network bottleneck.
📊 Impact: Eliminates redundant API calls during bulk merchandise creation, drastically reducing total execution time.
🔬 Measurement: Verified that multiple creations using the same blueprint will trigger only one network request per unique blueprint/provider combo.
PR created automatically by Jules for task 15644785792414516019 started by @merg357