issue_comments: 561900194
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/1385#issuecomment-561900194 | https://api.github.com/repos/pydata/xarray/issues/1385 | 561900194 | MDEyOklzc3VlQ29tbWVudDU2MTkwMDE5NA== | 1411265 | 2019-12-04T23:57:07Z | 2019-12-04T23:57:07Z | NONE | So is there any word on a best practice, fix, or workaround with the MFDataset performance? Still getting abysmal reading perfomance with a list of NetCDF files that represent sequential times. I want to use MFDataset to chunk multiple time steps into memory at once but its taking 5-10 minutes to construct MFDataset objects and even longer to run .values on it. |
{
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
224553135 |