search

flyteorg / flyte

Scalable and flexible workflow orchestration platform that seamlessly unifies data, ML and analytics stacks.
https://flyte.org
Apache License 2.0
5.47k stars 584 forks source link

[Core feature] [FlyteAdmin] Cache completed workflow execution status to speed up UI pages #2010

Open kumare3 opened 2 years ago

kumare3 commented 2 years ago

Motivation: Why do you think this is important?

Once a workflow reaches a terminal state, it does not get updated. Thus, we can simply cache the workflow execution status and some basic information in an LRU cache on each server. This should speed up access to these pages in Flyteconsole tremendously.

Goal: What should the final outcome look like, ideally?

The UI project/workflows page loads extremely fast.

Describe alternatives you've considered

Client side caching. This is already done, but we could ammortize the cache across multiple user sessions

Propose: Link/Inline OR Additional context

No response

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

Have you read the Code of Conduct?

github-actions[bot] commented 1 year ago

Hello 👋, This issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏

github-actions[bot] commented 1 year ago

Hello 👋, This issue has been inactive for over 9 months and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏

github-actions[bot] commented 2 months ago

Hello 👋, this issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will engage on it to decide if it is still applicable. Thank you for your contribution and understanding! 🙏