We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Motivation: Why do you think this is important? It can speed up progressing workflows drastically.
Goal: What should the final outcome look like, ideally? Propeller's algorithm today does the following:
With the change, it would: 1- Sync WFs from informer 2- Iterate on WFs 3- Traverse each and attempt to make progress 4- Store 5- If a change is detected (https://github.com/lyft/flytepropeller/blob/master/pkg/controller/handler.go#L212), go back to 3, if not, go to 6 6- Wait for next sync period.
Flyte component
The text was updated successfully, but these errors were encountered:
This has been merged and tested at scale. WE can observe and order of magnitude performance imrpovements
Sorry, something went wrong.
Bump core requirements to flytekit 0.31.0b4 (flyteorg#676)
6a8b4dd
Signed-off-by: Eduardo Apolinario <[email protected]> Co-authored-by: Eduardo Apolinario <[email protected]>
kumare3
No branches or pull requests
Motivation: Why do you think this is important?
It can speed up progressing workflows drastically.
Goal: What should the final outcome look like, ideally?
Propeller's algorithm today does the following:
With the change, it would:
1- Sync WFs from informer
2- Iterate on WFs
3- Traverse each and attempt to make progress
4- Store
5- If a change is detected (https://github.com/lyft/flytepropeller/blob/master/pkg/controller/handler.go#L212), go back to 3, if not, go to 6
6- Wait for next sync period.
Flyte component
The text was updated successfully, but these errors were encountered: