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: Introduce explicit priority for jobs #977

Merged
merged 3 commits into from
Jun 30, 2022
Merged

job: Introduce explicit priority for jobs #977

merged 3 commits into from
Jun 30, 2022

Conversation

radeksimko
Copy link
Member

@radeksimko radeksimko commented Jun 28, 2022

Fixes #962

I also found one more bug where we'd schedule new jobs as if they always involve closed directories - meaning that these would only get picked up by the lower-priority scheduler which is more likely to be busy indexing walked directories.

Therefore the fix (last commit) should further improve performance as we now correctly treat any new job for open directory as high priority.

UX Impact

This simulates 10sec delay when obtaining data from the Module Registry.

Before

Screen.Recording.2022-06-28.at.11.09.51.mov

After

Screen.Recording.2022-06-28.at.11.10.34.mov

@radeksimko radeksimko added the bug Something isn't working label Jun 28, 2022
@radeksimko radeksimko added this to the v0.29.0 milestone Jun 28, 2022
@radeksimko radeksimko marked this pull request as ready for review June 28, 2022 10:15
@radeksimko radeksimko requested a review from a team as a code owner June 28, 2022 10:15
Copy link
Member

@dbanck dbanck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

Having high and low priority jobs makes things a lot clearer than differentiating between open and closed dir jobs!

@radeksimko radeksimko merged commit 68e2bf6 into main Jun 30, 2022
@radeksimko radeksimko deleted the f-job-priority branch June 30, 2022 13:01
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 31, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

state: Allow setting explicit priority for any job
2 participants