-
Notifications
You must be signed in to change notification settings - Fork 2.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
Track the conversion of the benchmark to a real benchmark in skywalking exporter. #6116
Comments
@jpkrohling the issue has been created. |
@liqiangz Can you please provide more inputs about steps to track, I would like to give it a try :) |
Sure! This file contains a test that is measuring the time it takes for some operations: exporter/skywalkingexporter/skywalking_benchmark_test.go This thread is relevant for this task: https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/5690/files#r739082935 Ideally, we would be using real Go benchmarks, as described here: https://pkg.go.dev/testing#hdr-Benchmarks If benchmarking that isn't straightforward (I think it should), that source file should just be removed. The goal for that test is to assess that concurrent calls to opentelemetry-collector-contrib/exporter/skywalkingexporter/skywalking.go Lines 100 to 113 in 1e9005e
|
Hi @alolita, Please assign this to me. I would like to start working on this. |
Assigned. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
Pinging code owners: @liqiangz. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
@liqiangz, are you still the code owner for the component? |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
please assign to me |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
@wu-sheng , any chance we can get this done? |
@liqiangz Are you still on this? @jpkrohling I have no update about this too. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
Given that the component will be removed soon, this should be closed. |
Refer to #5690. This issue is to track the benchmark of skywalking exporter.
The text was updated successfully, but these errors were encountered: