-
Notifications
You must be signed in to change notification settings - Fork 4.5k
[BEAM-6908] Support Python3 performance benchmarks - part 2 #8324
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
Conversation
|
+R: @udim, |
|
run python postcommit |
udim
left a comment
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.
LGTM, but please wait for postcommits to be green before merging
|
Thank you. postcommit failed consistently for a while and got fixed recently (today?). I'll rebase and rerun them. Would like to merge this PR after Perfkit change merged in master to make the transition status as short as possible. |
|
run python postcommit |
|
Perfkit corresponding changes are merged in GoogleCloudPlatform/PerfKitBenchmarker@d0ad984. We now can merge this PR after tests pass. |
|
Run Java PreCommit |
1 similar comment
|
Run Java PreCommit |
|
Rebased this PR against master. |
|
Run Python_PVR_Flink PreCommit |
Support Python3 performance benchmarks - part 2
Keep use of Perfkit performance infrastructure for Python3 benchmarking due to exist integration with Python pipeline and automated metrics publishing. Part 1 changes are on PerfkitBenchmarker in GoogleCloudPlatform/PerfKitBenchmarker@d0ad984
Changes include in this PR:
PythonPerformanceTestConfigurationto make task construction clear and easier to maintain.enablePythonPerformanceTestinBeamModulePluginso that people can enable python performance test in different projects by simply calling this function.sdks/python/test-suites/dataflow/py3run_integration_test.shdue to wrong check order.Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
R: @username).[BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replaceBEAM-XXXwith the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.Post-Commit Tests Status (on master branch)
Pre-Commit Tests Status (on master branch)
See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.