-
-
Notifications
You must be signed in to change notification settings - Fork 18.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RLS: 1.3.1 #42343
Comments
for morale purposes, any perf improvements? |
|
rolling.EWMMethods.time_ewm -> @mroeschke is there a known cause for these? stat_ops.FrameOps.time_ops based on a quick look we're spending way more time inside ufunc _reduce. The affected cases are the tiny ones, so t |
|
The list posted in the OP is not filtered. I think all the relevant performace regression in that list now have issues. since the official benchmark machine only tracks master, I have unofficial results for 1.3.x at https://simonjayhawkins.github.io/fantastic-dollop/#regressions?sort=3&dir=desc&branch=1.3.x (where some are ignored) |
got it. if my post is extraneous feel free to delete |
not at all. |
Actually from the commit where the regression happened here, https://pandas.pydata.org/speed/pandas/#rolling.EWMMethods.time_ewm?python=3.8&Cython=0.29.21&p-constructor='DataFrame'&p-constructor='Series'&p-window=1000&p-dtype='float'&p-method='mean'&commits=ab687aec-f066cda6, the major thing was that we used to have 2 ewm algorithms that were essentially the same and they were combined, and the combined one does an extra power and div operations per value compared to the old implementation. The performance was somewhat ameliorated in #40164. |
@pandas-dev/pandas-core reminder that 1.3.1 is scheduled for end of this week. It is a calendar release so will not block on open PRs. (get them in early if to be included in 1.3.1.) |
will be moving open issues/ unfinished PRs on 1.3.1 milestone https://github.com/pandas-dev/pandas/milestone/87 to 1.3.2 milestone https://github.com/pandas-dev/pandas/milestone/88 tomorrow in readiness for release on Sunday. |
pre-release checklist
|
starting release now. 1.3.1 milestone closed off.
|
only linux_aarch64_numpy1.19python3.7.____73_pypy not yet built. |
this built fine on the PR https://cloud.drone.io/conda-forge/pandas-feedstock/129 but is timing out on the master build. Restarted several times yesterday and several times the day before. Have restarted again today to see if the situation is any better. |
linux_aarch64_numpy1.19python3.7.____73_pypy now built and available on conda-forge |
Tracking issue for the 1.3.1 release.
https://github.com/pandas-dev/pandas/milestone/87
Currently scheduled for July 25, 2021 (date flexible on severity of regressions)
List of open regressions: https://github.com/pandas-dev/pandas/issues?q=is%3Aopen+is%3Aissue+label%3ARegression
significant performance regressions between 1.2.5 and 1.3.0
cc @pandas-dev/pandas-core @pandas-dev/pandas-triage
The text was updated successfully, but these errors were encountered: