-
-
Notifications
You must be signed in to change notification settings - Fork 508
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
Panel adds considerable overhead to longer running async tasks #4239
Comments
It seems that Dask needs to be configured to handle long running python functions that do not release the GIL. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm trying to write a how to guide for Dask. I can see in the Dask efficiency docs that they expect one millisecond of overhead for submitting one task to Dask.
From my experiments this seems not to hold when used with Panel. The minimum overhead seems to be around 7 msecs. And what is worse, as the task duration grows so does the overhead. And its not insignificant.
cluster.py
tasks.py
app.py
I would have expected the overhead to stay constant. But it looks like it does not.
Maybe this is just a Dask thing. But I've not been able to find any statements that indicate this.
I've asked the questions in the Dask Discourse forum. See https://dask.discourse.group/t/why-does-submit-overhead-increase-exponentially-for-fibonacci-example/1420.
The text was updated successfully, but these errors were encountered: