Speakers list performance

Keep Admin → Speakers responsive for large events.

What good looks like

Admin → Speakers should remain interactive for large speaker graphs by using server-side search and pagination or bounded queries. Pulling the entire participation graph into the browser on every keystroke is not the intended pattern.

Operator practices

Search with specific tokens instead of empty broad loads when the UI offers query params. Avoid opening dozens of detail panels at once on low-memory devices. Prefer readiness outstanding lists when you only need people with incomplete tasks.

  1. Use the search box with a name or email fragment.
  2. Prefer readiness for overdue task hunts.
  3. Use CLI speakers list --event <id> --q <query> --json for agent reporting instead of scraping the DOM.
speakerops speakers list --event <eventId> --q 'Ada' --json

When something feels wrong

Check network panel for repeated full-list fetches. Confirm the event context is correct (wrong event may look empty or oddly large). Report regressions with HAR-free descriptions and correlation ids rather than production secrets.