Skip to content

⚡ Bolt: [performance improvement] Optimize dashboard KPIs queries#116

Open
bobdivx wants to merge 1 commit into
devfrom
bolt-kpis-optimize-15783700269297467889
Open

⚡ Bolt: [performance improvement] Optimize dashboard KPIs queries#116
bobdivx wants to merge 1 commit into
devfrom
bolt-kpis-optimize-15783700269297467889

Conversation

@bobdivx

@bobdivx bobdivx commented Jun 14, 2026

Copy link
Copy Markdown
Owner

💡 What:
Refactored the /api/dashboard-kpis.ts endpoint to use Drizzle ORM aggregation primitives (count(), gte(), inArray()) instead of fetching full tables into memory.

🎯 Why:
Previously, queries like db.select().from(AgentTask) were fetching potentially thousands of records into Node.js memory just to execute a .length operation. This caused an O(N) memory allocation scaling issue that degraded the dashboard's load performance.

📊 Impact:
Eliminates O(N) memory scaling for KPI database operations. Reduces Node.js memory usage and payload size significantly by offloading aggregations natively to SQLite.

🔬 Measurement:
Run the endpoint locally, memory utilization limits drop.


PR created automatically by Jules for task 15783700269297467889 started by @bobdivx

💡 What:
Refactored the `/api/dashboard-kpis.ts` endpoint to use Drizzle ORM aggregation primitives (`count()`, `gte()`, `inArray()`) instead of fetching full tables into memory.

🎯 Why:
Previously, queries like `db.select().from(AgentTask)` were fetching potentially thousands of records into Node.js memory just to execute a `.length` operation. This caused an O(N) memory allocation scaling issue that degraded the dashboard's load performance.

📊 Impact:
Eliminates O(N) memory scaling for KPI database operations. Reduces Node.js memory usage and payload size significantly by offloading aggregations natively to SQLite.

🔬 Measurement:
Run the endpoint locally, memory utilization limits drop.

Co-authored-by: bobdivx <6737167+bobdivx@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.

@vercel

vercel Bot commented Jun 14, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
forge Ready Ready Preview, Comment Jun 14, 2026 5:13pm

@gemini-code-assist gemini-code-assist Bot 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.

Code Review

This pull request refactors the /api/dashboard-kpis.ts endpoint to use Drizzle ORM aggregation functions (count(), gte(), inArray()) instead of fetching entire tables into memory and performing in-memory filtering. This change eliminates O(N) memory scaling bottlenecks for dashboard KPI queries. Additionally, a test file was removed, and a performance journal entry was added to document these findings. There are no review comments, and we have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

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