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

[wild-endeavor]

Describe the issue

Follow-up to flyteorg/flytekit#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?

• Yes

Have you read the Code of Conduct?

• Yes

[runllm]

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:

• Flyte documentation on optimizing tasks

---

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!