Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Job status websocket / websocket storm updates #5883

Closed
jakemcdermott opened this issue Feb 11, 2020 · 1 comment
Closed

Job status websocket / websocket storm updates #5883

jakemcdermott opened this issue Feb 11, 2020 · 1 comment

Comments

@jakemcdermott
Copy link
Contributor

jakemcdermott commented Feb 11, 2020

SUMMARY

We're going to add some new behavior to the websocket subscription flow in the API and UI. The goal is to address the "websocket storm" issue.

details

@ryanpetrello
Copy link
Contributor

@mabashian @jakemcdermott @rebeccahhh re the job list performance issue, I think we can make a lot of progress by just being smarter about the requests we make.

Here's an m5.4xl w/ 1M jobs and 1B+ job events:

image

Note if we drill down only to job IDs we care about (perhaps what just got sent over the websocket w/ a status change), things really get snappy:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants