-
Notifications
You must be signed in to change notification settings - Fork 750
Adds performance tests, that compare to published NuGet #975
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
not ready for runs yet, as I can't yet force the benchmark to use different assembly versions
Not sure I made the CI/build script changes correctly. Plus we might have to restrict testing to Python 3.5 for now, as it is the only version supported by a published NuGet. |
ad92f96
to
2e28711
Compare
Excluded CI changes so that this can be merged independently. |
327c311
to
6a9f75e
Compare
6a9f75e
to
250a490
Compare
Codecov Report
@@ Coverage Diff @@
## master #975 +/- ##
===========================================
+ Coverage 65.44% 86.71% +21.26%
===========================================
Files 1 1
Lines 301 301
===========================================
+ Hits 197 261 +64
+ Misses 104 40 -64
Continue to review full report at Codecov.
|
@filmor ready to review |
Add performance tests that compare to published NuGet
A new project
src\perf_tests\Python.PerformanceTests.csproj
, that uses BenchmarkDotNet to benchmark compare current version with the latest version published on NuGet (2.3 as of now).During build the baseline and new version are copied into separate directories. Benchmark code then loads new or baseline based on an environment variable.
In the end, an "optimistic performance ratio" is computed, that has to be less than some target (usually close to 1.0) for the performance test to pass.