Performance optimizations from the hackweek

[nickvergessen]

• Number of requests when switching a room
  • POST /active
  • DELETE /active
  • GET /signaling/settings (800ms?)
    • Brute force protection (GET /signaling/settings and more) kicks in and does not clear Always log the token and reset again when joining successfully #8712
      • Browser: 800ms ↘️ 50ms
  • GET History
  • GET New
    • Combine loading chat messages (single request for past + future) Load history and first set of new messages with 1 API request #8717
      • Server: 6 Request ↘️ 5 Requests
  • GET /participants
  • Heaviness of requests
• General UX
  • Pre-fetch some (so we don't DoS) chats (unread mentions first, max 5, …?) as the user is more likely to open them?
  • Reduce redrawing and the conversation list data that is grabbed every 30 seconds "Modified since" support on roomlist #8726
    - Browser: avg. 131 / max 706 ↘️ ~0-30 conversations redrawn every 30s
• Notifications UX
  • Up on notification arrival cheat the room list so that unread chats are visible
    • feat: Emit an event when a notification is received with background polling notifications#1450
    • feat(performance): Update conversation data for chat messages and cal… #8723
      • UX: random 1-30 sec ↘️ instantly updated without a request
  • Up on notification arrival pre-fetch messages so when the user goes there they are immediately visible
  • Avoid page reload when clicking "Show chat" or "Join call" when on talk already
    • Trigger a proper event-bus event notifications#728
    • feat(performance): Open conversations from notifications without page reload #8713
      • UX: Full page reload ↘️ Pageless opening when on Talk
  • Avoid page reload when the user clicks on a browser notification Focus the tab and allow pageless redirect for notification.onclick notifications#1448
    - UX: Full page reload ↘️ Pageless opening when on Talk

[SystemKeeper]

• POST /active

Could be an optional parameter in 2, to not make a separate request?

[nickvergessen]

Could be an optional parameter in 2, to not make a separate request?

Way too deep in the signalin code for a change like this.