-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Benchmark 0.5 vs 0.6 [do not merge] #20947
Conversation
Your benchmark job has completed - possible performance regressions were detected. A full report can be found here. cc @jrevels |
Not bad. Summary of stuff that got slower: Arrays:
Date accessors in generalFor example: Fixed by #20853? FactorizationsFor example:
|
Is it possible to test against 0.4 as well? |
Should be, let's try it! |
vs v0.4.7: @nanosoldier |
probably need an older copy of the saved data for 0.4 |
1ddf26f
to
9fbf9bb
Compare
Eeh what? I just rebased this branch and force pushed to it...? |
There's no more commit to merge on this anymore. |
Thought it would be a good time to start checking the performance vs 0.5. Easiest to have this in a branch since AFAIK there is no way to run a benchmark between two commits from an issue.
vs 0.5.1:
@nanosoldier
runbenchmarks(ALL, vs = "@6445c82d0060dbe82b88436f0f4371a4ee64d918")
Note to self, but [ci skip] on the commit for the rebases to come.