Skip to content

HAR analysis: Place insights page

Source: place-insights.har — opening the Place insights page (initial load / navigation from Launchpad or control room shell).

Flow: User navigates to the Place insights page. The page loads control room shell (control rooms list, preferences, config, apps), places, control room, tasks count, collaborators, and cycles.

API calls (observed)

API Count Notes
POST /cycles/summary?size=250 5× 2 pairs within 4ms and 3ms; one call took 3.1 s
GET /controlrooms?size=100 3×
GET /controlrooms/{id} 3×
GET /controlrooms/{id}/collaborators 3×
GET /controlrooms/{id}/config 2× ~53ms apart
GET /me/preferences?namespace=control-room-... 2× Same namespace
GET /controlrooms/{id}/places?size=250 2×
POST /tasks/{id}/search?size=1&page=0 2×
GET /controlrooms/{id}/apps, GET /me/preferences (cookiesPolicy, sidenav, whatsNew) 1× each Expected

Duplicated calls

  • cycles/summary — 5× total: two pairs fired within 4ms and 3ms (clear duplicates); one call took 3.1 s.
  • getControlRooms — 3×.
  • getControlRoom — 3×.
  • getCollaborators — 3×.
  • config — 2×.
  • me/preferences (control-room namespace) — 2× (same namespace).
  • places — 2× (same params).
  • tasks/search?size=1 — 2×.

Note: A different capture (longer session) may also show assets and events polling with two concurrent pollers, similar to Event insights.

Performance note

  • cycles/summary — One call took 3.1 s. Backend optimization would help.

Suggested fix

  • cycles/summary — Consolidate to 1×; share via store. Multiple components likely each trigger their own load.
  • Control room, control rooms list, config, collaborators, places, tasks — Use store when available.
  • me/preferences — Avoid duplicate fetches for same namespace.

Estimated impact

  • Duplicates: 5× cycles → 1×; 3× CR, control rooms, collaborators → 1× each; 2× config, places, tasks, preferences → 1× each. ~15 redundant calls in ~2s.
  • Slow cycles: 3.1s — backend tuning.