issue_comments: 306587426
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/1440#issuecomment-306587426 | https://api.github.com/repos/pydata/xarray/issues/1440 | 306587426 | MDEyOklzc3VlQ29tbWVudDMwNjU4NzQyNg== | 2443309 | 2017-06-06T19:10:27Z | 2017-06-06T19:10:27Z | MEMBER | I'd certainly support a warning when dask chunks do not align with the on-disk chunks. Beyond that, I think we could work on a utility for automatically determining chunks sizes for xarray using some heuristics. Before we go there though, I think we really should develop some performance benchmarks. We're starting to get a lot of questions/issues about performance and it seems like we need some benchmarking to happen before we can really start fixing the underlying issues. |
{
"total_count": 3,
"+1": 3,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
233350060 |