issue_comments: 177527321
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-177527321 | https://api.github.com/repos/pydata/xarray/issues/729 | 177527321 | MDEyOklzc3VlQ29tbWVudDE3NzUyNzMyMQ== | 306380 | 2016-01-31T15:32:44Z | 2016-01-31T15:33:01Z | MEMBER | Sorry for the delay in response. Nothing here seems dangerous to me. @shoyer does the writeup above raise any questions for you? If convenient, it would be interesting to see the output of a few of the dask profilers:
``` python import cachey from dask.diagnostics import CacheProfiler, ResourceProfiler, Profiler, visualize with Profiler() as prof, CacheProfiler(metric=cachey.nbytes) as cprof, ResourceProfiler() as rprof: # call the final dataset.to_netcdf() function visualize([prof, cprof, rprof], file_path='profile.html') ``` And then upload that file somewhere, perhaps to a gist. In order to make this run to completion you might have to operate on a subset of the dataset. Alternatively, is there a way for me to recreate a version of this dataset on my local machine? @shoyer is there a way to capture the metadata of netcdf files and reinstantiate empty copies of them on another machine? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
129150619 |