issue_comments: 184351600

This data as json

html_url issue_url id node_id user created_at updated_at author_association body reactions performed_via_github_app issue
https://github.com/pydata/xarray/issues/729#issuecomment-184351600 https://api.github.com/repos/pydata/xarray/issues/729 184351600 MDEyOklzc3VlQ29tbWVudDE4NDM1MTYwMA== 306380 2016-02-15T19:16:26Z 2016-02-15T19:16:26Z MEMBER

Looking at the task graph my first guess is that @shoyer is correct, and that we've found another case that the scheduler should be able to handle well, but doesn't. This hasn't happened in a while, but it always leads to improvements whenever we find such a problem.

For a case this complex I think we either need to reduce it to a particular graph motif on which we schedule poorly or we first need to develop a better way to visualize traces of the scheduler's behavior. I've started a separate dask issue: https://github.com/dask/dask/issues/994

For the near future I don't have a solution to @Scheibs 's research problem (sorry!) This will probably require tweaking dask scheduler internals which probably won't happen by me in the next couple of weeks. I'm very happy that people brought this to my attention though.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   129150619