Skip to content

⚡ Bolt: scope lesson progress database queries - #98

Open
projectamazonph wants to merge 1 commit into
mainfrom
fix/performance-lesson-progress-2367052442445887195
Open

⚡ Bolt: scope lesson progress database queries#98
projectamazonph wants to merge 1 commit into
mainfrom
fix/performance-lesson-progress-2367052442445887195

Conversation

@projectamazonph

Copy link
Copy Markdown
Owner

⚡ Bolt: scope lesson progress database queries

💡 What

Optimized user-specific lesson progress queries in src/app/(dashboard)/dashboard/page.tsx and src/app/(dashboard)/courses/page.tsx by scoping down the database queries to the specific lesson IDs fetched for the published courses (lessonId: { in: allLessonIds }).

🎯 Why

Previously, the code queried all user lesson progress rows without filter, meaning that as a user progresses through more courses and lessons over time, the payload fetched from PostgreSQL would grow unboundedly. This leads to high latency, huge DB payloads, and bloated memory usage.

📊 Impact

  • Reduces database round-trip payload size and network latency by only retrieving rows relevant to the courses displayed on the current page.
  • Prevents unbounded memory growth on the server as student progress scales.
  • Reduces CPU cycles spent parsing unnecessary Prisma JSON rows.

🔬 Measurement

Verify that pages load with scoped progress queries and that the test suite passes under DATABASE_URL environment variables. Ensure Next.js static page generation builds without any dynamically-rendered errors.


PR created automatically by Jules for task 2367052442445887195 started by @projectamazonph

Optimize db queries in dashboard and courses pages to only fetch
progress for lessons belonging to published courses.

Co-authored-by: projectamazonph <286085559+projectamazonph@users.noreply.github.com>
Copilot AI review requested due to automatic review settings July 30, 2026 13:55
@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.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@coderabbitai

coderabbitai Bot commented Jul 30, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@projectamazonph, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 17 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 579a25df-20a2-4006-b933-b01201f0e61c

📥 Commits

Reviewing files that changed from the base of the PR and between 9d0e0bf and f211647.

📒 Files selected for processing (3)
  • .jules/bolt.md
  • src/app/(dashboard)/courses/page.tsx
  • src/app/(dashboard)/dashboard/page.tsx

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

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.

2 participants