-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
add benchmark for the cloud output #1224
Conversation
The benchmark is testing only for httpext.Trail and such that have different urls and names which is probably the worst case performance wise. The benchmark is somewhat flaky ... but with more runs it seems consitant in 5% margins ;)
$ benchcmp -mag 9e1c5c1.perf 78858ef.perf
$ benchcmp -mag 78858ef.perf a948b4d.perf
$ benchcmp -mag a948b4d.perf 9554c6e.perf
$ benchcmp -mag 9554c6e.perf b6650a5.perf
|
Codecov Report
@@ Coverage Diff @@
## master #1224 +/- ##
==========================================
+ Coverage 75.12% 75.14% +0.01%
==========================================
Files 147 147
Lines 10709 10709
==========================================
+ Hits 8045 8047 +2
+ Misses 2199 2197 -2
Partials 465 465
Continue to review full report at Codecov.
|
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.
Hmm if I'm interpreting the results correctly, that seems like quite a regression in performance since 78858ef onwards. But it's an acceptable trade-off for the url=name
workaround, right?
My only concern would be adding even more flaky tests benchmarks. I think we have enough flakiness with tests already. :) And this won't be run in CI, right?
@imiric benchmarks are atm not ran by CI although around #1167 may change. |
Can you retry with |
@cuonglm
|
Thanks, seems to be a lot of noise when benchmark runs. But the result looks reasonable. |
The benchmark is testing only for httpext.Trail and such that have
different urls and names which is probably the worst case performance
wise. The benchmark is somewhat flaky ... but with more runs it seems
consitant in 5% margins ;)