From 512fabaf7472d2d9e1a8a9a8f5c23bc22485c3fc Mon Sep 17 00:00:00 2001 From: Vishal Sadriya Date: Sat, 7 Mar 2026 11:06:22 +0530 Subject: [PATCH] docs: simplify Performance at Scale section in README MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Remove implementation details (SQL queries, subqueries) — keep it user-facing with just the show_chart config option. --- README.md | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/README.md b/README.md index 2f78ba0..7ee1038 100644 --- a/README.md +++ b/README.md @@ -126,12 +126,7 @@ end ### Performance at Scale -SolidQueueMonitor is optimized for large datasets (millions of rows in `solid_queue_jobs`): - -- **Overview stats** are derived entirely from execution tables (`ready_executions`, `scheduled_executions`, `claimed_executions`, `failed_executions`), avoiding expensive `COUNT(*)` queries on the jobs table. -- **Chart data** uses SQL `GROUP BY` bucketing instead of loading timestamps into Ruby memory. -- **Filters** use subqueries (`.select(:job_id)`) instead of loading ID arrays into memory. -- **Queue stats** are pre-aggregated with `GROUP BY` to avoid N+1 queries. +SolidQueueMonitor is optimized for large datasets (millions of rows in `solid_queue_jobs`). All dashboard queries are designed to stay fast regardless of table size. If you don't need the job activity chart, disable it to skip chart queries entirely: