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

Abierto
  • ¿Algo no está bien?
#249 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
32/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
postgresql, sql, typescript
Área
backend, databases, performance

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
TypeScript
Estrellas
1
Forks
1
Merge medio
6 h 56 min
PR fusionados (30 d)
136

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de eddiejaoude/StackDash

Todos los issues de eddiejaoude/StackDash

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.