issue_comments: 308926818
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/pull/1457#issuecomment-308926818 | https://api.github.com/repos/pydata/xarray/issues/1457 | 308926818 | MDEyOklzc3VlQ29tbWVudDMwODkyNjgxOA== | 12229877 | 2017-06-16T03:57:57Z | 2017-06-16T03:57:57Z | CONTRIBUTOR | The tests for Hypothesis take almost twice as long to run on Travis at certain times of day, so I certainly wouldn't use it for benchmarking anything! Also concerned that a dedicated benchmarking machine may lead to software (accidentally!) optimized for a particular architecture or balance of machine resources without due consideration. Maybe @wesm could investigate fault injection to (eg) slow down disk access or add latency for some sets of benchmarks? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
236347050 |