PLUTO-134 Supabase Disk-IO budget alert (2026-06-15) disposition: reads clean (99.96% cached). Two analyses diverge on write driver — (1) */2 rate-spike cron churn vs (2) one-time Jun-14 PLUTO-128/130 DDL burst + pg_dump catalog walks. Discriminator = IO graph shape (spike=one-time self-clearing; plateau=cron lever PLUTO-67). GATED on Elazar interval ruling if plateau. No compute upgrade warranted.

PLUTO-134 · pluto

Supabase Disk-IO budget alert (2026-06-15) disposition: reads clean (99.96% cached). Two analyses diverge on write driver — (1) */2 rate-spike cron churn vs (2) one-time Jun-14 PLUTO-128/130 DDL burst + pg_dump catalog walks. Discriminator = IO graph shape (spike=one-time self-clearing; plateau=cron lever PLUTO-67). GATED on Elazar interval ruling if plateau. No compute upgrade warranted.

No sub-items.

No questions.

2026-06-15T16:19:50.655Z · created · wi-cli-venus
2026-06-16T02:05:27.990Z · completed · wi-cli-venus

Disk-IO ~3k IOPS spike = benign: the every-8h evolutiva-backup@pluto pg_dump full-DB sequential read (~53MB burst). pg_stat_statements shows no high-IO query signature (total shared_blks_read ~1253), clean PG logs (tiny checkpoints, no slow/seq-scan/heavy-autovacuum). No query to fix, no action.