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/pull/6542#issuecomment-1122811102,https://api.github.com/repos/pydata/xarray/issues/6542,1122811102,IC_kwDOAMm_X85C7Lze,3019665,2022-05-10T20:06:06Z,2022-05-10T20:06:06Z,NONE,"> @jakirkham were you thinking a reference to the dask docs for more info on optimal chunk sizing and aligning with storage?

It could make sense to refer to or if similar ideas come up here it may be worth mentioning in this change

> or are you suggesting the proposed docs change is too complex?

Not at all.

> I was trying to address the lack of documentation on specifying chunks within a zarr array for _non-dask_ arrays/coordinates, but also covering the weedsy (but common) case of datasets with a mix of dask & in-memory arrays/coords like in my example. I have been frustrated by zarr stores I've written with a couple dozen array chunks and thousands of coordinate chunks for this reason, but it's definitely a gnarly topic to cover concisely :P

If there's anything you need help with or would like to discuss, please don't hesitate to raise [a Zarr issue]( https://github.com/zarr-developers/zarr-python/issues ). We also enabled GH discussions over there so if that fits better feel free to use that 🙂","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1221393104
https://github.com/pydata/xarray/pull/6542#issuecomment-1121430268,https://api.github.com/repos/pydata/xarray/issues/6542,1121430268,IC_kwDOAMm_X85C16r8,3019665,2022-05-09T18:23:03Z,2022-05-09T18:23:03Z,NONE,FWIW there's a similar [doc page about chunk size in Dask]( https://docs.dask.org/en/stable/array-best-practices.html#select-a-good-chunk-size ) that may be worth borrowing from,"{""total_count"": 1, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 1}",,1221393104