Serve the timeline's connection counts from a rollup once workspaces reach millions of events

Aperta
  • Qualcosa non va?
#249 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
32/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
postgresql, sql, typescript
Ambito
backend, databases, performance

Direzione di ricerca

Start by reading the activity_event_daily_counts rollup and its statement-level triggers from #201, then the query behind timeline_connection_event_counts and the pgTAP cases in supabase/tests/database/21_timeline_connection_event_counts.test.sql. Decide between extending the rollup with connection_id/severity or adding a sibling rollup, and reconcile London filter days against UTC rollup days. Done means the unfiltered badge renders under 100 ms at 2.3M events with explain analyze on the PR and the pgTAP cases unchanged and passing.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area: timeline enhancement impact: low priority: P3 size: M

Summary

The timeline's connection badges (#245, PR #248) are counted by timeline_connection_event_counts, which aggregates the workspace's activity_events on every timeline render. With no filters, that reads every event the workspace keeps. Retention keeps 13 months (HISTORY_RETENTION_MONTHS in src/lib/jobs/retention.ts).

Measured with explain analyze on committed data in an isolated Postgres 17.11 container (the supabase/postgres:17.11.0.011 image, default settings):

Workspace size Filter Execution time
23,000 events (local demo) none 5.5 ms
2.3 million events (#191 scale, 13 months) none 134 to 148 ms
2.3 million events severity critical 88 ms
2.3 million events last 30 days 54 ms
2.3 million events one day 1 ms

The unfiltered case at #191 scale is over the 100 ms interactive read budget. #245 accepted this, because no workspace is near that size today. This issue holds the follow-up.

Scope

  • Extend the activity_event_daily_counts rollup (#201) with connection_id and severity, or add a sibling rollup, kept by the same statement-level triggers.
  • Serve the badges from the rollup when the filters allow it: no date filter, or whole days. The timeline's date filter uses London days and the rollup uses UTC days, so a filtered window that does not line up with UTC days still needs the live table, or a London-day rollup.
  • Keep the rule that a badge counts exactly what the timeline lists. Reuse the supabase/tests/database/21_timeline_connection_event_counts.test.sql cases against the new path.

Acceptance criteria

  • The unfiltered badges for a 2.3 million event workspace render under 100 ms (explain analyze quoted on the PR).
  • The counts are unchanged for every filter combination covered by the pgTAP test.

Model: anthropic/claude-opus-5-5 | Reasoning effort: unknown

Lingua principale
TypeScript
Stelle
1
Fork
1
Merge medio
6h 56m
PR unite (30g)
136

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di eddiejaoude/StackDash

Tutte le issue di eddiejaoude/StackDash

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.