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

[Docs] Enhance performance optimization guide #5745

Open
2 tasks done
davidmirror-ops opened this issue Sep 13, 2024 · 1 comment
Open
2 tasks done

[Docs] Enhance performance optimization guide #5745

davidmirror-ops opened this issue Sep 13, 2024 · 1 comment
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@davidmirror-ops
Copy link
Contributor

Description

This docs page was recently updated but some issues persist and should be addressed to avoid users spending time trying to configure parameters that are not located where they should be or trying to understand obscure concepts.

  1. The keys in the Configuration parameter in this table refer to backend plugin workers and not core.propeller settings.
  2. For some users it's still not clear from the explanation in this section if parameters like workflow-reeval-duration or downstream-eval-duration should be increased or decreased to prevent propeller to pick new workflow evaluations more often than checking existing workflow state.

@cpaulik please add more gaps if you find them

Are you sure this issue hasn't been raised already?

  • Yes

Have you read the Code of Conduct?

  • Yes
@davidmirror-ops davidmirror-ops added documentation Improvements or additions to documentation untriaged This issues has not yet been looked at by the Maintainers labels Sep 13, 2024
@cpaulik
Copy link
Contributor

cpaulik commented Sep 17, 2024

In terms of explanation the streak-length is also quite unclear to me.

I was not able to understand what it actually does from the docs but in terms of just optimising the value.

The current page says

Larger values can lead to faster completion times for workflows that benefit from continuous processing, especially cached or computationally intensive workflows,

and at the same time that lower values are

effectively prioritizing fast-changing or “hot” workflows.

It's unclear to me what workflows that benefit from continuous processing are and how they are different from prioritizing fast-changing or “hot” workflows

@eapolinario eapolinario removed the untriaged This issues has not yet been looked at by the Maintainers label Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Status: Backlog
Development

No branches or pull requests

4 participants