P95 Query Time

P95 Query Time

The 95th percentile database query duration — 95% of queries complete faster than this. Weighted by execution frequency across all queries. Slow queries are often caused by missing indexes or N+1 patterns.

34 ms

0.3%

Compared to previous 7 days

Execution Rate

Query Execution Rate

Total database queries executed over the last 14 days, expressed as an average rate. Spikes may indicate N+1 queries or inefficient data access patterns.

2.65 / hour

1.4%

Compared to previous 7 days

Query Responses

Query Responses

This panel shows all executions of this query, including performance metrics, duration distribution, and query execution details.

Reset
Click marker to copy SHA
Time Period Executions Avg Duration Min Duration Max Duration ▲
Sep 16, 2026 55 19.56 ms 1.0 ms 35.0 ms
Sep 17, 2026 46 18.93 ms 1.0 ms 35.0 ms
Sep 18, 2026 66 18.98 ms 2.0 ms 35.0 ms
Sep 19, 2026 59 18.0 ms 1.0 ms 35.0 ms
Sep 20, 2026 71 19.59 ms 1.0 ms 35.0 ms
Sep 21, 2026 56 18.13 ms 1.0 ms 35.0 ms
Sep 22, 2026 69 18.32 ms 1.0 ms 35.0 ms
Sep 23, 2026 27 16.26 ms 1.0 ms 35.0 ms
Sep 12, 2026 62 20.95 ms 3.0 ms 36.0 ms
Sep 13, 2026 62 18.16 ms 2.0 ms 39.0 ms
Total of 15 record(s).
Page 1 of 2

Normalized Query 

SELECT name FROM users

Diagnostics

Query Diagnostics

Automatically generated analysis for this query. Includes N+1 detection (from live request data), query characteristics, detected issues, optimization suggestions, and a database EXPLAIN plan. Click Re-analyze to regenerate.

Query Characteristics
Query Type
SELECT
Tables
1
Joins
0
Complexity Score
2
Has LIMIT
No
Has ORDER BY
No
Has GROUP BY
No
Has Subqueries
No
Issues Detected
  • SELECT query without WHERE clause may return excessive data
Optimization Suggestions
  • Use includes() to eager load associations — Eliminate N+1 queries and reduce database load
  • Use joins() when you only need to filter, not access associated data — Eliminate N+1 queries and reduce database load
  • Use preload() when you don't need to query on associations — Eliminate N+1 queries and reduce database load
  • Add WHERE clause to filter results — Avoid full table scans and reduce data transfer
Execution Plan
2 | 0 | 216 | SCAN users

Query Locations

Query Locations

Shows where in your codebase this query originates, based on the last 30 days of executions. P95 duration and row count highlight the worst-case performance at each call site.

Location P95 Duration (ms) P95 Row Count Count
app/controllers/admin_controller.rb:67 34.0 — 497
app/jobs/import_job.rb:73 33.0 — 1
app/jobs/image_processing_job.rb:92 30.0 — 1
app/mailers/user_mailer.rb:28 39.0 — 1

Raw Data 

{
  "query": {
    "id": 80,
    "normalized_sql": "SELECT name FROM users",
    "analyzed_at": "2026-09-23 06:02:25 UTC"
  },
  "performance": {
    "total_executions": 500,
    "p95_duration_ms": "34.0",
    "avg_duration_ms": 18.71,
    "p95_row_count": null,
    "avg_row_count": null
  },
  "characteristics": {
    "query_type": "SELECT",
    "table_count": 1,
    "join_count": 0,
    "where_clause_complexity": 0,
    "has_subqueries": false,
    "has_limit": false,
    "has_order_by": false,
    "has_group_by": false,
    "has_having": false,
    "has_distinct": false,
    "has_aggregations": false,
    "estimated_complexity": 2
  },
  "call_locations": [
    {
      "location": "app/controllers/admin_controller.rb:67",
      "count": 497,
      "p95_duration_ms": "34.0",
      "p95_row_count": null
    },
    {
      "location": "app/jobs/import_job.rb:73",
      "count": 1,
      "p95_duration_ms": "33.0",
      "p95_row_count": null
    },
    {
      "location": "app/jobs/image_processing_job.rb:92",
      "count": 1,
      "p95_duration_ms": "30.0",
      "p95_row_count": null
    },
    {
      "location": "app/mailers/user_mailer.rb:28",
      "count": 1,
      "p95_duration_ms": "39.0",
      "p95_row_count": null
    }
  ],
  "n_plus_one": {
    "detected": false
  },
  "index_recommendations": [],
  "issues": [
    "SELECT query without WHERE clause may return excessive data"
  ],
  "explain_plan": "2 | 0 | 216 | SCAN users"
}