Skip to content

docs: simplify Performance at Scale section in README #29

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vishaltps merged 1 commit into from
Mar 7, 2026
Merged

docs: simplify Performance at Scale section in README #29

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 1 addition & 6 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down