[Docs] Default container limits not documented

[Mathis-Z]

Description

I setup Flyte on minikube and was wondering why my hello-world container took over a minute to run. I found this thread explaining the issue: https://discuss.flyte.org/t/9458852/hey-there-we-are-noting-some-relatively-high-latency-for-sim
Essentially, Flyte will set a default cpu request and limit of 0.1 so the container is throttled by default. I think this is unexpected behavior (I would expect no default limit and a reasonable minimum request) and should be documented or maybe even changed in the code.

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

• Yes

Have you read the Code of Conduct?

• Yes

[welcome]

Thank you for opening your first issue here! 🛠

[runllm]

Flyte sets default resource requests and limits for tasks, which can lead to throttling if not adjusted. By default, Flyte may set a low CPU request and limit, such as 0.1, which can cause high latency in task execution, especially in environments like minikube where resources are limited. This behavior is not explicitly documented, leading to unexpected performance issues for users.

Would you like more details on how to adjust these defaults or further information on Flyte's resource management?

Sources:

• Flyte Task Resource Management

---

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!