issues: 171957028
This data as json
| id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 171957028 | MDU6SXNzdWUxNzE5NTcwMjg= | 976 | Document performance tips for using dask with xarray | 1217238 | closed | 0 | 2 | 2016-08-18T17:32:14Z | 2019-01-22T20:24:15Z | 2019-01-22T20:24:15Z | MEMBER | A few dask array limitations lead to frequent performance issues for xarray users: https://github.com/dask/dask/issues/746 https://github.com/dask/dask/issues/874 Since these are non-trivial to solve on the dask side, we should document (in our page on dask) how to work around them for xarray users. This mailing list post has most of the relevant advice: https://groups.google.com/forum/#!topic/xarray/11lDGSeza78 CC @mrocklin @jcrist |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/976/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
completed | 13221727 | issue |