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.74k stars 652 forks source link

[Housekeeping] flytekit friendly client should potentially make more use of lru cache #5695

Open wild-endeavor opened 2 months ago

wild-endeavor commented 2 months ago

Describe the issue

Follow-up to https://github.com/flyteorg/flytekit/pull/2714 where get_X was cached (since we're pretty confident these calls always return the same information).

What if we do not do this?

potentially wasted calls.

Related component(s)

No response

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

Have you read the Code of Conduct?

runllm[bot] commented 2 months ago

The issue you mentioned is not explicitly covered in the provided data sources. However, it relates to optimizing Flyte's client by using an LRU (Least Recently Used) cache to avoid redundant calls, which can improve performance by caching frequently accessed data.

Would you like more details on Flyte's caching mechanisms or potential workarounds for optimizing client calls?

Sources:

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @runllm to ask follow-up questions. See runllm.com for more!