You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A user reported that they are running sky launch but they find sky launch on existing cluster is very slow and the expect behavior is that:
if cluster does not exist, provision the cluster and run the job
if the cluster exists, run the job only (like exec), and skip all those time consuming steps, including skypilot runtime setup, waiting for ssh, and user setup.
Two ways to achieve this:
Make the sky launch super fast on an existing cluster by caching the current state of a cluster and only re-setup the cluster when the runtime is stale.
add an option to automatically use sky.exec when sky launch is run on an existing cluster.
The text was updated successfully, but these errors were encountered:
Michaelvll
changed the title
[UX] Launch should skip the provisioner path when calling again
[UX] Launch on existing cluster should be very fast
Oct 23, 2024
This is mostly solved by sky launch --fast.
This is not turned on by default since it's very hard to tell when setup should be re-run.
We could probably turn the provisioning short-circuit in #4289 on by default.
A user reported that they are running
sky launch
but they findsky launch
on existing cluster is very slow and the expect behavior is that:Two ways to achieve this:
sky launch
super fast on an existing cluster by caching the current state of a cluster and only re-setup the cluster when the runtime is stale.sky.exec
whensky launch
is run on an existing cluster.The text was updated successfully, but these errors were encountered: