ClusterCockpit/cc-backend
1
0
Fork 0
mirror of https://github.com/ClusterCockpit/cc-backend synced 2026-03-15 04:17:30 +01:00
Code Issues Packages Releases Activity

Consolidate migrations

Browse Source 
Entire-Checkpoint: a3dba4105838
This commit is contained in:
Jan Eitzinger
2026-03-13 17:14:13 +01:00
parent ba366d0d72
commit e83bd2babd
9 changed files with 77 additions and 86 deletions
Download Patch File Download Diff File Expand all files Collapse all files

61
internal/repository/migrations/sqlite3/11_optimize-indexes.up.sql
View File

@@ -1,8 +1,8 @@
-- Migration 11: Remove overly specific table indexes formerly used in sorting
-- When one or two indexed columns are used, sorting usually is fast
-- Reduces from ~78 indexes to 48 for better write performance,
-- reduced disk usage, and more reliable query planner decisions.
-- Requires ANALYZE to be run after migration (done automatically on startup).
-- Migration 11: Optimize job table indexes
-- - Remove overly specific sorting indexes (reduces ~78 → 48)
-- - Add covering index for grouped stats queries
-- - Add covering indexes for status/dashboard queries
-- - Add partial covering indexes for running jobs (tiny B-tree)
-- ============================================================
-- Drop SELECTED existing job indexes (from migrations 08/09)
@@ -57,5 +57,54 @@ DROP INDEX IF EXISTS jobs_cluster_arrayjobid_starttime;
-- Backup Indices For High Variety Columns
DROP INDEX IF EXISTS jobs_duration;
-- Optimize DB index usage
-- ============================================================
-- Covering indexes for grouped stats queries
-- Column order: cluster (equality), hpc_user/project (GROUP BY), start_time (range scan)
-- Includes aggregated columns to avoid main table lookups entirely.
-- ============================================================
CREATE INDEX IF NOT EXISTS jobs_cluster_user_starttime_stats
ON job (cluster, hpc_user, start_time, duration, job_state, num_nodes, num_hwthreads, num_acc);
CREATE INDEX IF NOT EXISTS jobs_cluster_project_starttime_stats
ON job (cluster, project, start_time, duration, job_state, num_nodes, num_hwthreads, num_acc);
-- ============================================================
-- Covering indexes for status/dashboard queries
-- Column order: cluster (equality), job_state (equality), grouping col, then aggregated columns
-- These indexes allow the status views to be served entirely from index scans.
-- ============================================================
-- Drop 3-col indexes that are subsumed by the covering indexes below
DROP INDEX IF EXISTS jobs_cluster_jobstate_user;
DROP INDEX IF EXISTS jobs_cluster_jobstate_project;
CREATE INDEX IF NOT EXISTS jobs_cluster_jobstate_user_stats
ON job (cluster, job_state, hpc_user, duration, start_time, num_nodes, num_hwthreads, num_acc);
CREATE INDEX IF NOT EXISTS jobs_cluster_jobstate_project_stats
ON job (cluster, job_state, project, duration, start_time, num_nodes, num_hwthreads, num_acc);
CREATE INDEX IF NOT EXISTS jobs_cluster_jobstate_subcluster_stats
ON job (cluster, job_state, subcluster, duration, start_time, num_nodes, num_hwthreads, num_acc);
-- ============================================================
-- Partial covering indexes for running jobs
-- Only running jobs are in the B-tree, so these indexes are tiny compared to
-- the full-table indexes above. SQLite uses them when the query contains the
-- literal `job_state = 'running'` (not a parameter placeholder).
-- ============================================================
CREATE INDEX IF NOT EXISTS jobs_running_user_stats
ON job (cluster, hpc_user, num_nodes, num_hwthreads, num_acc, duration, start_time)
WHERE job_state = 'running';
CREATE INDEX IF NOT EXISTS jobs_running_project_stats
ON job (cluster, project, num_nodes, num_hwthreads, num_acc, duration, start_time)
WHERE job_state = 'running';
CREATE INDEX IF NOT EXISTS jobs_running_subcluster_stats
ON job (cluster, subcluster, num_nodes, num_hwthreads, num_acc, duration, start_time)
WHERE job_state = 'running';
PRAGMA optimize;