issue_comments: 469898607
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/2799#issuecomment-469898607 | https://api.github.com/repos/pydata/xarray/issues/2799 | 469898607 | MDEyOklzc3VlQ29tbWVudDQ2OTg5ODYwNw== | 5635139 | 2019-03-05T23:16:43Z | 2019-03-05T23:16:43Z | MEMBER |
Right, tbc, I'm only referring to the top two lines of the pasted benchmark; i.e. once we enter python (even if only to access a numpy array) we're already losing a lot of the speed relative to the loop staying in C / Cython. So even if xarray were a python front-end to a C++ library, it still wouldn't be competitive if performance were paramount. ...unless pypy sped that up; I'd be v interested to see. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
416962458 |