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/6309#issuecomment-1094086518,https://api.github.com/repos/pydata/xarray/issues/6309,1094086518,IC_kwDOAMm_X85BNm92,90008,2022-04-09T17:06:13Z,2022-04-09T17:06:13Z,CONTRIBUTOR,"@max-sixty unfortunately, I think the way hdf5 is designed, it doesn't try to be too smart about what would be the best fine tuning for your particular system. In some ways, this is the correct approach.

The current constructor pathway:
https://github.com/pydata/xarray/blob/main/xarray/backends/h5netcdf_.py#L164

Doesn't provide a user with a catchall-kwargs. I think this would be an acceptable solution.

I should say that the the performance of the direct driver is terrible without aligned data:
https://github.com/Unidata/netcdf-c/pull/2206#issuecomment-1054855769","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1152047670
https://github.com/pydata/xarray/issues/6309#issuecomment-1052386013,https://api.github.com/repos/pydata/xarray/issues/6309,1052386013,IC_kwDOAMm_X84-uiLd,90008,2022-02-26T17:57:33Z,2022-02-26T17:57:33Z,CONTRIBUTOR,"I have to elaborate that this may be even more important for users that READ the data back alot. Reading with the standard Xarray operands hits other limits, but one limit that it definitely hits is that of the HDF5 driver used.

","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1152047670