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.2%

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

11.7%

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 25 18.28 ms 5.0 ms 33.0 ms
Sep 22, 2026 49 17.92 ms 1.0 ms 34.0 ms
Sep 21, 2026 50 18.88 ms 1.0 ms 35.0 ms
Sep 20, 2026 79 18.35 ms 1.0 ms 35.0 ms
Sep 19, 2026 71 17.58 ms 1.0 ms 35.0 ms
Sep 18, 2026 64 19.97 ms 1.0 ms 35.0 ms
Sep 17, 2026 57 18.86 ms 1.0 ms 35.0 ms
Sep 16, 2026 72 18.08 ms 1.0 ms 35.0 ms
Sep 15, 2026 62 18.23 ms 1.0 ms 49.0 ms
Sep 14, 2026 60 15.6 ms 1.0 ms 46.0 ms
Total of 15 record(s).
Page 1 of 2

Normalized Query 

SELECT * FROM posts WHERE title LIKE ? AND content LIKE ? AND LOWER(title) LIKE ? AND UPPER(content) LIKE ?

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
10
Has LIMIT
No
Has ORDER BY
No
Has GROUP BY
No
Has Subqueries
No
Issues Detected
  • Using SELECT * may retrieve unnecessary columns
Optimization Suggestions
  • Add composite index: add_index :posts, ["title", "content"] — Efficient multi-column filtering
    add_index :posts, ["title", "content"]
Execution Plan
2 | 0 | 216 | SCAN posts

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": 89,
    "normalized_sql": "SELECT * FROM posts WHERE title LIKE ? AND content LIKE ? AND LOWER(title) LIKE ? AND UPPER(content) LIKE ?",
    "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": 8,
    "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": 10
  },
  "call_locations": [],
  "n_plus_one": {
    "detected": false
  },
  "index_recommendations": [
    "add_index :posts, [\"title\", \"content\"]"
  ],
  "issues": [
    "Using SELECT * may retrieve unnecessary columns"
  ],
  "explain_plan": "2 | 0 | 216 | SCAN posts"
}