Skip to content

HAR analysis: Event insights page

Source: event-insights.har — opening the Event insights page.

Flow: User navigates to the Event insights page. The page loads assets, events (search + polling), collaborators, control room, event insight search, tasks count, preferences, places, cycles, and polls for updates.

API calls (observed)

API Count Notes
GET /controlrooms/{id}/collaborators 2× ~530ms apart
POST /cycles/summary?size=250 2× Same request within 1ms — clear duplicate
GET /controlrooms/{id}/assets?size=250&recordedAfter=... 7× Two pollers; each poll fires 2 requests with slightly different recordedAfter
POST /events/search?after=... 4× Polling for new events (by design)
POST /events/search?isEventInsightSearch=true&size=250&page=0 1× 4.1 s — main event insight search; dominant latency
GET /controlrooms/{id}, tasks/search, me/preferences, places 1× each

Duplicated calls

  • getCollaborators — 2× (same pattern as other pages).
  • cycles/summary — 2× within 1ms — identical request; clear duplicate.
  • assets — 7× over ~15s; appears to be two concurrent pollers (e.g. two components) each fetching assets with slightly different recordedAfter. One poller would suffice.

Performance note (non-duplicate)

  • events/search?isEventInsightSearch=true — 4.1 s. Main event insight search; consider backend optimization or pagination.

Suggested fix

  • Collaborators — Use store when available.
  • cycles/summary — Consolidate to 1×; share via store.
  • Assets polling — Single poller; share data via store or shared service.
  • Event insight search — Backend: profile query; consider caching or reducing scope.

Estimated impact

  • Duplicates: 2× collaborators + 2× cycles/summary + ~3–4× redundant assets polls → 1× each. ~5–6 calls saved per 15s window.
  • Slow search: 4.1s — backend tuning.