Actions
Bug #23117
closed
Websocket flood slows down process page
Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Workbench2
Target version:
Story points:
-
Release:
Release relationship:
Auto
Description
Process page with many active suprocesses gets spammed with websocket messages that slow down the page.
Websocket handler needs additional throttles for page refreshes to prevent this
Files
Updated by Stephen Smith 7 months ago
- Related to Bug #23083: Data explorer apparently enters an infinite loop (sometimes?) when loading All Processes added
Updated by Stephen Smith 7 months ago
- File main.569c9160.js main.569c9160.js added
Changes at arvados|bea8e2c811b076bd132734b557229aad5764977c branch 23117-websocket-flood-bug
Tests developer-run-tests-services-workbench2: #1579
- Added throttles to the last 2 things websocket updates can trigger - process page refresh and collection refresh just to be safe.
Production bundle attached
Updated by Lucas Di Pentima 7 months ago
Bundle's behavior on a ~300 running container looks promising, a lot snappier and constant refreshes are not evident anymore.
Updated by Stephen Smith 7 months ago
Changes at arvados|66159d6429c3e81c6378d6b331c10a0913360e88 branch 23117-websocket-flood-bug
Tests developer-run-tests-services-workbench2: #1580
- All agreed upon points are implemented / addressed.
- Added 15s throttles to collection and process page refreshes
- Added explicit refresh after renaming files to avoid relying on the throttled websocket background updates to update the UI after file rename actions
- Added cy.clock 15 second fast forward to test when testing background refresh
- Anything not implemented (discovered or discussed during work) has a follow-up story.
- none
- Code is tested and passing, both automated and manual, what manual testing was done is described
- Passed manual test and automated background refresh tests
- Documentation has been updated.
- n/a
- Behaves appropriately at the intended scale (describe intended scale).
- n/a
- Considered backwards and forwards compatibility issues between client and server.
- none
- Follows our coding standards and GUI style guidelines.
- yes
Updated by
Updated by Stephen Smith 7 months ago
- Status changed from New to Resolved
Updated by
Actions