home / github / issue_comments

Menu
  • Search all tables
  • GraphQL API

issue_comments: 510217080

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/2501#issuecomment-510217080 https://api.github.com/repos/pydata/xarray/issues/2501 510217080 MDEyOklzc3VlQ29tbWVudDUxMDIxNzA4MA== 1312546 2019-07-10T20:30:41Z 2019-07-10T20:30:41Z MEMBER

Yep, that’s my suspicion as well. I’m still plugging away at it. Currently the pausing logic isn’t quite working well.

On Jul 10, 2019, at 12:10, Ryan Abernathey notifications@github.com wrote:

I believe that the memory issue is basically the same as dask/distributed#2602.

The graphs look like: read --> rechunk --> write.

Reading and rechunking increase memory consumption. Writing relieves it. In Rich's case, the workers just load too much data before they write it. Eventually they run out of memory.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  372848074
Powered by Datasette · Queries took 235.408ms · About: xarray-datasette