#2010 [Core feature] [FlyteAdmin] Cache completed workflow execution status to speed up UI pages Issue created by kumare3 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? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#2010 [Core feature] [FlyteAdmin] Cache completed workflow execution status to speed up UI pages Issue closed as not planned by github-actions[bot] flyteorg/flyte