Skip to content

⚡ Optimize N+1 Query in Brand Product Updates#400

Draft
syed-reza98 wants to merge 2 commits intomainfrom
performance-brand-product-updates-optimization-8658153721038947235
Draft

⚡ Optimize N+1 Query in Brand Product Updates#400
syed-reza98 wants to merge 2 commits intomainfrom
performance-brand-product-updates-optimization-8658153721038947235

Conversation

@syed-reza98
Copy link
Copy Markdown
Collaborator

💡 What:

Optimized assignProductsToBrand and removeProductsFromBrand in BrandService by replacing the N+1 database query loop with a more efficient batch operation.

🎯 Why:

The previous implementation performed one updateMany call for every product ID in the provided array. This resulted in significant performance overhead when processing large batches of products (e.g., assigning hundreds of products to a brand).

📊 Measured Improvement:

  • Database Operations: Reduced from $N$ queries (where $N$ is the number of product IDs) to exactly 2 queries (1 findMany + 1 updateMany).
  • Input Efficiency: Added deduplication for the provided product IDs.
  • Safety: Maintained the same data integrity checks (storeId, deletedAt, and brandId) in the batch update as in the original sequential updates.
  • Error Handling: Preserved the original logic's ability to report specific missing or inaccessible product IDs.

PR created automatically by Jules for task 8658153721038947235 started by @syed-reza98

- Replaced sequential `prisma.product.updateMany` calls with bulk `findMany` and `updateMany` operations in `BrandService`.
- Reduced complexity from $O(N)$ database queries to $O(1)$ (exactly 2 queries: one to verify existence/accessibility and one to perform the update).
- Maintained detailed error reporting by identifying missing products before the update.
- Added input deduplication with `Set`.
- Created comprehensive unit tests in `src/test/services/brand.service.test.ts` to verify the optimization and correctness.

Co-authored-by: syed-reza98 <71028588+syed-reza98@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.

@vercel
Copy link
Copy Markdown

vercel bot commented Mar 30, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
stormcomui Ready Ready Preview, Comment Mar 30, 2026 1:55pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

1 participant