issue_comments: 932811398

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/5764#issuecomment-932811398 https://api.github.com/repos/pydata/xarray/issues/5764 932811398 IC_kwDOAMm_X843mZKG 1312546 2021-10-02T19:48:05Z 2021-10-02T19:48:05Z MEMBER

Mmm for better or worse, Dask relies on sizeof to estimate the memory usage of objects at runtime. We could move that over to some new duck-typed interface like using .nbytes if it's around, but not all objects will want to expose an nbytes attribute in their API.

IMO, I think the best path is for objects to implement __getsizeof__ unless there's some downside I'm missing.

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