performance

Enforce server-side aggregation and explicit column selection for data queries.

19|13|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/stahura/domo-ai-vibe-rules --skill performance-stahura
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performance
Source: https://github.com/stahura/domo-ai-vibe-rules/tree/main/skills/custom-apps/performance
Command: npx skills add https://github.com/stahura/domo-ai-vibe-rules --skill performance-stahura

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies and enforces best practices for data query performance, guiding how data is shaped, filtered, and aggregated to minimize payload and maximize responsiveness.

Core Features & Use Cases

  • Server-side aggregation using grouping and sum/count operations to return only essential results.
  • Explicit column selection to fetch only the necessary fields, reducing data transfer and processing.
  • Guidance for common patterns like totals, filtered counts, and per-visualization queries to support scalable dashboards.

Quick Start

Provide a dataset and group by a suitable column (e.g., region) with aggregations to enable server-side reduction of data before visualization.

Frequently Asked Questions about performance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What's the best way to optimize query speed for large analytical dashboards?

Query speed optimization for large analytical dashboards is achieved by enforcing targeted data retrieval and efficient server-side aggregation. Applying explicit column selection and grouping data before visualization minimizes payload and reduces latency.

How do I reduce data payload latency when fetching large datasets for reports?

Data payload latency is reduced by avoiding fetch-all patterns and using explicit column selection. Fetching only the necessary fields minimizes data transfer and processing overhead before the data reaches the client.

When should I use server-side aggregation versus client-side computation?

Server-side aggregation should be used over client-side computation when handling large datasets for reports. Grouping by columns and performing sum or count operations on the server returns only essential results and prevents client-side bottlenecks.

How do I structure a query for per-visualization data in scalable dashboards?

Per-visualization queries for scalable dashboards are structured by applying server-side groupBy operations with specific aggregations. This targeted retrieval pattern ensures each visualization receives only the essential grouped data it needs.

Why does fetching all records slow down my dashboard performance?

Fetching all records slows down dashboard performance because it transfers unnecessary data and increases processing latency. Avoiding fetch-all patterns and using server-side aggregation with explicit column selection minimizes the payload.

Does server-side groupBy work for filtered counts and totals in reports?

Server-side groupBy works for filtered counts and totals by applying aggregations directly on the server. This approach supports scalable dashboards by returning only the essential summarized results instead of raw rows.