https://flyte.org logo
Join Slack
Powered by
Hi everyone :wave: just getting started with Flyte...
# flyte-support
n
Hi everyone 👋 just getting started with Flyte and I have a question about task latency. I have a basic workflow consisting of one 
ContainerTask
and one regular python task. Running it with 
pyflyte run
locally finishes in under a second. But running with the flyte sandbox as a remote 
pyflyte run --remote
it takes over 2 minutes according to the UI. Is this expected? It does eventually finish, Is there a timeout or something that can be configured? Details -> https://gist.github.com/perrygeo/05b438430ab776786bdc85185360c327
Looking at the k3s pods while it's running and I see the 
flyte-copilot-sidecar
container which appears to be idle. The actual task container itself is completed, it looks like the extra time is waiting for the sidecar to exit?
f
you can always configure timeouts on every task type
it can take time depending on if it is spinning up pods
if you want performance, then I recommend to use Union - it has ways to reuse containers and hence can run things in under a second
also can you try running it repeatedly, it might take a few seconds still
once the container has been downloaded
But the way to think about performance is overhead vs runtime and reproducibility and ephemerality. For example for non latency sensitive applications this is ok - especially it tears down the entire cluster when no one is using it
and multiple folks can run different version concurrently with low resources
4 Views
Open in Slack
PreviousNext
Powered by