pull_requests: 1577658012

This data as json

id node_id number state locked title user body created_at updated_at closed_at merged_at merge_commit_sha assignee milestone draft head base author_association auto_merge repo url merged_by
1577658012 PR_kwDOAMm_X85eCSac 8389 closed 0 Use numbagg for `ffill` by default 5635139 The main perf advantage here is the array doesn't need to be unstacked & stacked, which is a huge win for large multi-dimensional arrays... (I actually was hitting a memory issue running an `ffill` on my own, and so thought I'd get this done!) We could move these methods to `DataWithCoords`, since they're almost the same implementation between a `DataArray` & `Dataset`, and exactly the same for numbagg's implementation --- For transparency — the logic of "check for numbagg, check for bottleneck" I wouldn't rate at my most confident. But I'm more confident that just installing numbagg will work. And if that works well enough, we could consider only supporting numbagg for some of these in the future. I also haven't done the benchmarks here — though the functions are relatively well benchmarked at numbagg. I'm somewhat trading off getting through these (rolling functions are coming up too) vs. doing fewer slower, and leaning towards the former, but feedback welcome... <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] Tests added - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` - [x] New functions/methods are listed in `api.rst` 2023-10-28T20:40:13Z 2023-11-25T21:06:10Z 2023-11-25T21:06:09Z 2023-11-25T21:06:09Z a6837909ded8c3fe2d9ff8655b04d18f46d77ed5     0 7693b8520541fbe97134ea18b7ece9cdea5c95ad dc66f0d2b34754fb2a8d29d8eb635a5b143755ad MEMBER   13221727 https://github.com/pydata/xarray/pull/8389  

Links from other tables