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/6308#issuecomment-1301908749,https://api.github.com/repos/pydata/xarray/issues/6308,1301908749,IC_kwDOAMm_X85NmY0N,226720,2022-11-03T10:36:30Z,2022-11-03T10:36:30Z,NONE,"> Vanilla Xarray + Numpy has none of these problems because everything is in memory.

This is my understanding of xarray. Or is there a way that a xarray variable points to a dask structure?

> But isn't it fundamentally a Dask issue?

Dask has already some `performance_report` capabilities documented on https://docs.dask.org/en/stable/diagnostics-distributed.html#capture-diagnostics. Anything missing out there?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1151751524