-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Added end to end test for mem ballast #80
Conversation
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
@@ -188,3 +158,81 @@ func Test1000SPSWithAttributes(t *testing.T) { | |||
}) | |||
} | |||
} | |||
|
|||
|
|||
func Test1000SPSWithAttributes(t *testing.T) { |
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 test with ballast specifies the same expectedMaxCPU as the one without ballast. However test results that you posted show that with ballast it actually uses less CPU. So, perhaps tighten a bit expectedMaxCPU in this test? I suggest you leave about 30% of slack in CPU (that was my rule of thumb when writing other perf tests).
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 think I did reduce the numbers before creating the PR. Probably I missed something in the first push. In any case, updated the numbers and reduced them a further.
testbed/tests/results/TESTRESULTS.md
Outdated
TestBallast1000SPSWithAttributes/0*0bytes|PASS | 12s| 21.9| 25.3| 73| 114| 10000| 10000 | ||
TestBallast1000SPSWithAttributes/100*50bytes|PASS | 12s| 60.2| 68.3| 498| 847| 10000| 10000 | ||
TestBallast1000SPSWithAttributes/10*1000bytes|PASS | 12s| 41.0| 45.3| 354| 576| 9990| 9990 | ||
TestBallast1000SPSWithAttributes/20*5000bytes|PASS | 12s| 64.4| 74.0| 780| 1079| 9990| 9990 |
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.
This is a nice CPU improvement.
Codecov Report
@@ Coverage Diff @@
## master #80 +/- ##
=========================================
Coverage ? 69.77%
=========================================
Files ? 101
Lines ? 6392
Branches ? 0
=========================================
Hits ? 4460
Misses ? 1698
Partials ? 234 Continue to review full report at Codecov.
|
* Update the Agent architecture graph. * Fix a typo.
@owais Build status is not reported from Travis. You may want to restart. |
Looks like a bug. The build has passed: https://travis-ci.org/open-telemetry/opentelemetry-service/builds/552958842?utm_source=github_status&utm_medium=notification I don't have the option to restart builds for this repo and it's PRs. |
It will restart automatically after you merged the other PR and rebase this one. |
Build failed because of #43 |
Yea, I've been seeing quite a few random failures. Will rebase after we merge #85 |
@owais did you make changes or just rebased? If you need to rebase it is better to use "Update branch" button in Github. It reruns CI, but does not invalidate reviews (unlike rebasing and pushing the branch manually, which requires re-approval). So you don't need to ask for reapproval in that case. |
@tigrannajaryan I rebased. Update branch features ends up creating a merge commit as it merges master into the branch. Is that acceptable? |
This commit adds an end to end test to verify performance gain acheived with memory ballast It mainly checks the CPU usage and does not test against memory usage. I'll be submitting another PR that will specifically test memory behaviour and ensure the ballast does not actually consume memory. `TestNoBackend10kSPS` test was very reliably consuming >20 CPU on my machine so I increased the accepted values to 30 for this test.
@owais I don't think this is true. If I remember correctly when you merge the PR, the commit is squashed and rebased, no merge commit is created. |
CI hit #59 |
I see. I meant it creates a merge commit in the branch when updating from master but that wouldn't matter if the repo has only "squash and merge" available. Update again. Thanks. |
* add support for Link. * add AddLink to mockSpan * update api documentation.
This commit adds an end to end test to verify performance gain acheived
with memory ballast
It mainly checks the CPU usage and does not test against memory usage.
I'll be submitting another PR that will specifically test memory
behaviour and ensure the ballast does not actually consume memory.
TestNoBackend10kSPS
test was very reliably consuming >20 CPU on mymachine so I increased the accepted values to 30 for this test.