-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[benchmark][NFC] Use Swift naming conventions #39336
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
Capitalizing function names is against Swift naming conventions.
@swift-ci benchmark |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
What. The code size changes I think I understand -- these tests are now exporting arrays instead of just standalone BenchmarkInfo values. The change in |
…hmarks It just produces unnecessary code sign churn.
@swift-ci test |
@swift-ci benchmark |
Performance (x86_64): -O
Code size: -O
Performance (x86_64): -Osize
Code size: -Osize
Performance (x86_64): -Onone
Code size: -swiftlibsHow to read the dataThe tables contain differences in performance which are larger than 8% and differences in code size which are larger than 1%.If you see any unexpected regressions, you should consider fixing the Noise: Sometimes the performance results (not code size!) contain false Hardware Overview
|
@swift-ci benchmark |
Performance (x86_64): -O
Code size: -O
Performance (x86_64): -Osize
Code size: -Osize
Performance (x86_64): -Onone
Code size: -swiftlibsHow to read the dataThe tables contain differences in performance which are larger than 8% and differences in code size which are larger than 1%.If you see any unexpected regressions, you should consider fixing the Noise: Sometimes the performance results (not code size!) contain false Hardware Overview
|
Weird; it looks like the compiler decided to unroll the loop over |
My local benchmark results for Merging. |
Update benchmarks to bring them in line with basic Swift naming conventions.
Hopefully this will make working with benchmarks a little bit less scary for new contributors.
benchmarks
property.