-
Notifications
You must be signed in to change notification settings - Fork 38
Add performance testing start #220
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
base: master
Are you sure you want to change the base?
Add performance testing start #220
Conversation
* Add parquet import and update documentation --------- Co-authored-by: Torsten Kilias <[email protected]>
test/integration/performance/connection_http_transport_benchmark_test.py
Outdated
Show resolved
Hide resolved
test/integration/performance/connection_http_transport_benchmark_test.py
Outdated
Show resolved
Hide resolved
test/integration/performance/connection_http_transport_benchmark_test.py
Outdated
Show resolved
Hide resolved
test/integration/performance/connection_http_transport_benchmark_test.py
Outdated
Show resolved
Hide resolved
test/integration/performance/connection_http_transport_benchmark_test.py
Outdated
Show resolved
Hide resolved
test/integration/performance/connection_http_transport_benchmark_test.py
Outdated
Show resolved
Hide resolved
test/integration/performance/connection_http_transport_benchmark_test.py
Outdated
Show resolved
Hide resolved
test/integration/performance/connection_http_transport_benchmark_test.py
Outdated
Show resolved
Hide resolved
480285c
to
833dafe
Compare
…ministic header auto-generate
3396fab
to
5371a3e
Compare
1.3755199900000434, | ||
2.322247650999998, | ||
2.1706722630000286, | ||
7.116984646999981, |
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.
The imports outlier's don't look random, mostly the round before the last is slow. Maybe we force a flush to disk of the uncommitted data at this point, because we don't cleanup.
5.422284263999927, | ||
5.473687115000075, | ||
10.43289915999992, | ||
5.8234761429999935 |
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.
Again
6.998409852999998, | ||
7.840330088999963, | ||
7.807797928000014, | ||
12.746238112000015, |
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.
Again
2.009181237000007, | ||
2.81157267399999, | ||
2.7745194739999306, | ||
7.796403220000002, |
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.
Again
import_params={"columns": ["SALES_TIMESTAMP", "PRICE", "CUSTOMER_NAME"]}, | ||
) | ||
|
||
benchmark.pedantic(func_to_be_measured, iterations=1, rounds=benchmark_specs.rounds) |
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 saw a setup or teardown parameter
setup (callable) –
A function to call right before calling the target function in the first iteration of every round.
teardown (callable) –
A function to call after the last iteration of every round.
https://share.google/HYkd8TJRkLTfIVe8H
Because we use iterations 1 and multiple rounds, we should be able to cleanup for each measurement
1428eb4
to
6eed5a1
Compare
closes #211
Checklist
Note: If any of the items in the checklist are not relevant to your PR, leave the box unchecked.
For any Pull Request
Is the following correct:
When Changes Were Made
Did you:
When Preparing a Release
Have you: