-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
DOC: update link in benchmarks.md #57903
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
DOC: update link in benchmarks.md #57903
Conversation
web/pandas/community/benchmarks.md
Outdated
@@ -75,5 +75,5 @@ There is a quick summary here: | |||
|
|||
The main benchmarks comparing dataframe tools that include pandas are: | |||
|
|||
- [H2O.ai benchmarks](https://h2oai.github.io/db-benchmark/) | |||
- [DuckDB benchmarks](https://duckdblabs.github.io/db-benchmark/) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it'd be good to mention that those were the former H20.ai benchmarks. Maybe something as simple as this:
- [DuckDB benchmarks](https://duckdblabs.github.io/db-benchmark/) | |
- [DuckDB (former H20.ai) benchmarks](https://duckdblabs.github.io/db-benchmark/) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good. Thanks for your suggestion.
/preview |
Website preview of this PR available at: https://pandas.pydata.org/preview/pandas-dev/pandas/57903/ |
Thank you @yukikitayama, very nice! |
Thanks for your review @datapythonista 👍 |
doc/source/whatsnew/vX.X.X.rst
file if fixing a bug or adding a new feature.The H20.ai benchmark link in the benchmarks webpage contains the outdated benchmark results (e.g. the last benchmark was performed July 2021 and it used the pandas==1.2.5). DuckDB published a new benchmark results (e.g. the last benchmark was December 2023 with pandas==2.1.1) in the link with the same approach described in their blog. So it's a good idea to replace the benchmark link. Thank you @rootsmusic for the issue.