Skip to content

Prep for 0.1.0rc2 #86

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

Merged
merged 8 commits into from
Apr 2, 2025
Merged

Prep for 0.1.0rc2 #86

merged 8 commits into from
Apr 2, 2025

Conversation

robtandy
Copy link
Contributor

@robtandy robtandy commented Mar 20, 2025

This PR is long but it does not affect the core functionality of DataFusion for Ray, and does not differ from 0.1.0rc1 which has been extensively used by me in benchmarking from test.pypi.

This PR, when merged should be tagged 0.1.0rc2 and I can push the artifacts created by CI to test.pypi. Upon successful tests, these same artifacts can be used for the actual 0.1.0 release.

Also, fixes #85

This PR squashed merged the work that represented building out a repeatable k8s benchmarking set up. It is far from perfect but it has enabled significant benchmarking that has resulted in intuition around execution, latency, and price trade offs that I think will help us communicate about the project. The scripts and instructions are written to start from a fresh ubuntu 24.04 ami on amazon, and will work on arm or x86_64 architectures.

Summary of changes

  • k8s benchmarking scripts and instructions - the bulk of the PR
  • format python code
  • remove the last mentions of worker and replace with processor where appropriate to indicate DFRayProcessors
  • adding benchmark results in doc/benchmarks

@robtandy
Copy link
Contributor Author

@andygrove Here is the PR I mentioned to you that I would submit with benchmarking code and results.

I have some good graphs of the results, but i'll submit them in a subsequent PR post the 0.1.0rc2 tagging (that I request here)

@andygrove
Copy link
Member

This PR, when merged should be tagged 0.1.0rc2 and I can push the artifacts created by CI to test.pypi. Upon successful tests, these same artifacts can be used for the actual 0.1.0 release.

We'll also need the formal vote before making an official release.

Copy link
Member

@andygrove andygrove left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @robtandy!

@andygrove andygrove merged commit 1c63e85 into apache:main Apr 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Need to update project name
2 participants