New RunLLM response generated: >>>*# Question* Follow up question: static workflow inputs are promises, which seems to make it not possible to use workflow inputs to dynamically configure resources with

with_overrides

. The only way I see to do that is to pass the workflow inputs into a

@dynamic

workflow where the inputs are not promises, but that has the downside of executing an additional pod to run the dynamic workflow which adds significant additional latency. Am I missing something? # Answer You are correct that static workflow inputs are promises, which makes it challenging to use them directly for dynamic resource configuration with

with_overrides

. The workaround you mentioned, using a

@dynamic

workflow, is indeed a common approach to handle this, but it does introduce additional latency due to the extra pod execution. According to this discussion, the

with_overrides

method can be used within dynamic workflows to set resource limits dynamically based on inputs. However, this approach does involve the overhead of an additional pod. As of now, there is no alternative method explicitly documented to dynamically configure resources in a static workflow without converting inputs from promises. This limitation has been acknowledged in various discussions within the Flyte community, such as this GitHub issue. Would you like more details on this or potential workarounds? Sources: - Flyte Discussion on Resource Limits - Flyte GitHub Issue on Dynamic Workflows Slack Link https://flyte-org.slack.com/archives/CP2HDHKE1/p1719496612.655789 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.