Skip to content

⚡ Bolt: Cache Printify API variant lookups#56

Open
merg357 wants to merge 1 commit into
mainfrom
bolt-cache-printify-variants-15255439505164766462
Open

⚡ Bolt: Cache Printify API variant lookups#56
merg357 wants to merge 1 commit into
mainfrom
bolt-cache-printify-variants-15255439505164766462

Conversation

@merg357

@merg357 merg357 commented Jun 3, 2026

Copy link
Copy Markdown
Owner

💡 What: Implemented @functools.lru_cache on the get_variants function across printify_manager.py, create_merch.py, and merch_factory.py to memoize HTTP request results, storing them as immutable tuples.
🎯 Why: In bulk creation loops, querying the same blueprint's variants repeatedly causes an N+1 API call bottleneck. Caching these responses drastically reduces redundant network requests. Returning immutable tuples ensures thread safety and protects the cached data from unintended mutations downstream.
📊 Impact: Reduces redundant N+1 Printify API queries down to a single network call per unique blueprint and provider combination, significantly accelerating product creation times and minimizing API rate limiting.
🔬 Measurement: Verify by executing creation scripts (e.g., python3 create_merch.py) and observing the dramatically reduced network latency when looking up variants for multiple products of the same blueprint.


PR created automatically by Jules for task 15255439505164766462 started by @merg357

Applied `@functools.lru_cache` to `get_variants` in `printify_manager.py`, `create_merch.py`, and `merch_factory.py` to memoize the API responses as immutable tuples. This prevents N+1 network requests during bulk product creation.

Co-authored-by: merg357 <221854052+merg357@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown

👋 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