obmp-docker/postgres/scripts/011_ip_rib_perf_tuning.sql

43 lines
2.1 KiB
MySQL
Raw Permalink Normal View History

-- 011_ip_rib_perf_tuning.sql
-- Runtime performance tuning for ip_rib, derived from the 2026-05-19 ingestion
-- stress-test session. Idempotent.
--
-- Background: psql-app's unicast_prefix drain rate caps at a few-hundred msg/s
-- under continuous Postgres maintenance (autovacuum on ip_rib +
-- update_global_ip_rib() / update_chg_stats() / update_peer_rib_counts()
-- crons) competing for ip_rib disk I/O. Two levers applied here:
--
-- 1) Per-table autovacuum on ip_rib: lower scale_factor so autovacuum runs
-- more often on smaller chunks instead of one long disk-storm per cycle
-- (cost_limit kept high so each run finishes fast -- short intense
-- bursts let the consumer run flat out between them).
--
-- 2) Drop four unused/redundant ip_rib indexes (every INSERT updates every
-- index; these had 0 scans across ~2h of fleet convergence + storms +
-- operator activity). 9 -> 5 indexes; ~3.4 GB freed.
-- - ip_rib_hash_id_idx (907 MB, btree hash_id; the composite
-- pkey is (peer_hash_id, hash_id) so a
-- hash_id-alone index has no caller)
-- - ip_rib_base_attr_hash_id_idx (558 MB, no reverse-join caller)
-- - ip_rib_prefix_idx (1538 MB, GiST prefix inet_ops; only
-- used by ad-hoc prefix-containment
-- queries -- recreate if needed)
-- - ip_rib_origin_as_idx (364 MB, btree origin_as; the composite
-- (peer_hash_id, origin_as) handles
-- most ASN queries)
--
-- Recovery for dropped indexes (no downtime):
-- CREATE INDEX CONCURRENTLY ip_rib_prefix_idx ON ip_rib USING gist (prefix inet_ops);
-- CREATE INDEX CONCURRENTLY ip_rib_origin_as_idx ON ip_rib (origin_as);
-- ... etc.
ALTER TABLE ip_rib SET (
autovacuum_vacuum_scale_factor = 0.02,
autovacuum_analyze_scale_factor = 0.02
);
DROP INDEX IF EXISTS ip_rib_hash_id_idx;
DROP INDEX IF EXISTS ip_rib_base_attr_hash_id_idx;
DROP INDEX IF EXISTS ip_rib_prefix_idx;
DROP INDEX IF EXISTS ip_rib_origin_as_idx;