Florian Jetter

> Other tangential question: Can the tick rate of the dashboard be adjusted somehow? I would be totally fine with an update every 10s or so, I'm mostly using internal...

Well, I think this is neither a bug nor a feature. It's a bit of both I would say. Dask is internally relying on the structure of the keys and...

Queuing is not exactly what you are imagining I think. The queuing refers to when we are submitting a task to a worker and not when that work is actually...

> From what you are saying though, it sounds like the work is immediately scheduled to the least busy worker, even if there is technically no available resource on that...

without a reproducer I cannot help, unfortunately.

I believe the uproot5 problem also goes back to this line. If that issue persists, please point me to a fail case to investigate

Yes, this appears to be a typo. Looks like this is untested. Are you interested in contributing a patch (with a test)?

> I learned that right now for every task the scheduler creates a new connection This isn't true. We're opening a single connection between each worker and the scheduler. This...

The documentation wasn't updated but that's intended after https://github.com/dask/dask/pull/11844 To compute, use `dask.compute(fut)`

xref https://github.com/dask/dask/issues/9969