Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Subsecond cluster startup time #6413

Closed
mrocklin opened this issue May 23, 2022 · 1 comment · Fixed by #6415
Closed

Subsecond cluster startup time #6413

mrocklin opened this issue May 23, 2022 · 1 comment · Fixed by #6415

Comments

@mrocklin
Copy link
Member

We used to be able to start up clusters in tens of milliseconds. Now it takes a second or two.

In [1]: from dask.distributed import LocalCluster

In [2]: %%time
   ...: with LocalCluster(processes=False, n_workers=0):
   ...:     pass
   ...: 
CPU times: user 751 ms, sys: 68.5 ms, total: 819 ms
Wall time: 2.79 s

In [3]: %%time
   ...: with LocalCluster(processes=False, n_workers=0):
   ...:     pass
   ...: 
CPU times: user 73.4 ms, sys: 28 µs, total: 73.4 ms
Wall time: 1.08 s

This would make testing nicer.

@mrocklin
Copy link
Member Author

Looking at this, it looks like SpecCluster calls self.scheduler_comm.terminate(), the Scheduler calls Server.close, which waits a second for all comms to close, but there is still a comm asking us to terminate which is still active.

mrocklin added a commit to mrocklin/distributed that referenced this issue May 23, 2022
This permits servers to allow "terminate" comms to persist  when
shutting down.

Closes dask#6413
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant