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

12.5%

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.

14.0 / day

25.0%

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.

Click marker to copy SHA
Time Period ▼ Executions Avg Duration Min Duration Max Duration
Sep 22, 2026 7 17.0 ms 1.0 ms 27.0 ms
Sep 21, 2026 10 18.8 ms 4.0 ms 30.0 ms
Sep 20, 2026 18 16.28 ms 1.0 ms 35.0 ms
Sep 19, 2026 11 25.55 ms 12.0 ms 35.0 ms
Sep 18, 2026 11 20.55 ms 1.0 ms 34.0 ms
Sep 17, 2026 14 18.57 ms 5.0 ms 33.0 ms
Sep 16, 2026 13 21.77 ms 6.0 ms 35.0 ms
Sep 15, 2026 21 19.9 ms 1.0 ms 45.0 ms
Sep 14, 2026 14 17.57 ms 1.0 ms 32.0 ms
Sep 13, 2026 22 22.27 ms 1.0 ms 49.0 ms
Total of 14 record(s).
Page 1 of 2

Normalized Query 

SELECT posts.title, posts.content, users.name FROM posts JOIN users ON posts.user_id = users.id WHERE posts.published = ?

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
2
Joins
1
Complexity Score
8
Has LIMIT
No
Has ORDER BY
No
Has GROUP BY
No
Has Subqueries
No
Optimization Suggestions
  • Add single_column index: add_index :posts, :published — Fast lookups for published = value queries
    add_index :posts, :published
  • Add single_column index: add_index :posts, :user_id — Fast JOIN execution
    add_index :posts, :user_id
Execution Plan
3 | 0 | 216 | SCAN posts
7 | 0 | 45 | SEARCH users USING INTEGER PRIMARY KEY (rowid=?)

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.

No data available

No location data available.

Location data is captured when codebase_location is present on operations.

Raw Data 

{
  "query": {
    "id": 72,
    "normalized_sql": "SELECT posts.title, posts.content, users.name FROM posts JOIN users ON posts.user_id = users.id WHERE posts.published = ?",
    "analyzed_at": "2026-09-23 06:02:25 UTC"
  },
  "performance": {
    "total_executions": 0,
    "p95_duration_ms": null,
    "avg_duration_ms": null,
    "p95_row_count": null,
    "avg_row_count": null
  },
  "characteristics": {
    "query_type": "SELECT",
    "table_count": 2,
    "join_count": 1,
    "where_clause_complexity": 1,
    "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": 8
  },
  "call_locations": [],
  "n_plus_one": {
    "detected": false
  },
  "index_recommendations": [
    "add_index :posts, :published",
    "add_index :posts, :user_id",
    "add_index :posts, [\"published\", \"posts.title\", \"posts.content\", \"users.name\"], name: 'covering_idx_posts_published'"
  ],
  "issues": [],
  "explain_plan": "3 | 0 | 216 | SCAN posts\n7 | 0 | 45 | SEARCH users USING INTEGER PRIMARY KEY (rowid=?)"
}