issue_comments

Table actions

4 rows where issue = 334366223 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

author_association 3

issue 1

  • Slow performance with isel on stacked coordinates · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
632337326 https://github.com/pydata/xarray/issues/2241#issuecomment-632337326 https://api.github.com/repos/pydata/xarray/issues/2241 MDEyOklzc3VlQ29tbWVudDYzMjMzNzMyNg== stale[bot] 26384082 2020-05-21T20:48:13Z 2020-05-21T20:48:13Z NONE

In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity

If this issue remains relevant, please comment here or remove the stale label; otherwise it will be marked as closed automatically

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Slow performance with isel on stacked coordinates 334366223
399192741 https://github.com/pydata/xarray/issues/2241#issuecomment-399192741 https://api.github.com/repos/pydata/xarray/issues/2241 MDEyOklzc3VlQ29tbWVudDM5OTE5Mjc0MQ== nbren12 1386642 2018-06-21T18:03:05Z 2018-06-21T18:03:05Z CONTRIBUTOR

Thanks for the tips everyone. From the dask issue above, it appears that dask.reshape does not respect the boundaries of chunks. Therefore, pulling the first chunk of the stacked array requires pulling several chunks from the original un-reshaped data. This is a bit odd because the first chunk of the stacked array could just be a reshaped version of the first chunk from the unstacked array.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Slow performance with isel on stacked coordinates 334366223
399190064 https://github.com/pydata/xarray/issues/2241#issuecomment-399190064 https://api.github.com/repos/pydata/xarray/issues/2241 MDEyOklzc3VlQ29tbWVudDM5OTE5MDA2NA== max-sixty 5635139 2018-06-21T17:53:58Z 2018-06-21T17:53:58Z MEMBER

On that thread, quick shout out for https://github.com/joerick/pyinstrument, which I've found very intuitive for working out where in the stack is taking time; particularly when a function higher in the stack is calling fast functions many times

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Slow performance with isel on stacked coordinates 334366223
399181992 https://github.com/pydata/xarray/issues/2241#issuecomment-399181992 https://api.github.com/repos/pydata/xarray/issues/2241 MDEyOklzc3VlQ29tbWVudDM5OTE4MTk5Mg== rabernat 1197350 2018-06-21T17:26:58Z 2018-06-21T17:26:58Z MEMBER

%prun and snakeviz are very useful for performance analysis. When debugging dask performance, I also find it very useful to call .visualize() on the dask array. That shows you how dask is doing its thing under the hood.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Slow performance with isel on stacked coordinates 334366223

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);