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.

33 ms

1.6%

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.72 / hour

2.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 23, 2026 15 19.33 ms 1.0 ms 35.0 ms
Sep 22, 2026 64 17.2 ms 1.0 ms 35.0 ms
Sep 21, 2026 57 19.14 ms 1.0 ms 35.0 ms
Sep 20, 2026 69 18.96 ms 1.0 ms 35.0 ms
Sep 19, 2026 60 19.33 ms 2.0 ms 35.0 ms
Sep 18, 2026 78 16.94 ms 1.0 ms 35.0 ms
Sep 17, 2026 69 19.1 ms 1.0 ms 34.0 ms
Sep 16, 2026 50 17.3 ms 1.0 ms 35.0 ms
Sep 15, 2026 71 17.15 ms 1.0 ms 39.0 ms
Sep 14, 2026 73 18.26 ms 2.0 ms 35.0 ms
Total of 15 record(s).
Page 1 of 2

Normalized Query 

SELECT DISTINCT users.*, posts.*, comments.* FROM users, posts, comments WHERE users.id = posts.user_id AND posts.id = comments.post_id AND users.created_at > ? AND posts.created_at > ? AND comments.created_at > ?

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
7
Has LIMIT
No
Has ORDER BY
No
Has GROUP BY
No
Has Subqueries
No
Optimization Suggestions
  • Add composite index: add_index :users, ["id", "created_at"] — Efficient multi-column filtering
    add_index :users, ["id", "created_at"]
Execution Plan
7 | 0 | 210 | SCAN comments USING INDEX index_comments_on_post_id
12 | 0 | 45 | SEARCH posts USING INTEGER PRIMARY KEY (rowid=?)
17 | 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": 87,
    "normalized_sql": "SELECT DISTINCT users.*, posts.*, comments.* FROM users, posts, comments WHERE users.id = posts.user_id AND posts.id = comments.post_id AND users.created_at > ? AND posts.created_at > ? AND comments.created_at > ?",
    "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": 1,
    "join_count": 0,
    "where_clause_complexity": 5,
    "has_subqueries": false,
    "has_limit": false,
    "has_order_by": false,
    "has_group_by": false,
    "has_having": false,
    "has_distinct": true,
    "has_aggregations": false,
    "estimated_complexity": 7
  },
  "call_locations": [],
  "n_plus_one": {
    "detected": false
  },
  "index_recommendations": [
    "add_index :users, [\"id\", \"created_at\"]",
    "add_index :users, :created_at"
  ],
  "issues": [],
  "explain_plan": "7 | 0 | 210 | SCAN comments USING INDEX index_comments_on_post_id\n12 | 0 | 45 | SEARCH posts USING INTEGER PRIMARY KEY (rowid=?)\n17 | 0 | 45 | SEARCH users USING INTEGER PRIMARY KEY (rowid=?)"
}