You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Improve performance of createAndFinishSpanForOtelSpan #15864
I'd like to take this. I'll first add a focused benchmark around createAndFinishSpanForOtelSpan, profile its hot allocations/calls, then make the smallest change that preserves span timestamps, status, attributes, links, and parent relationships. I'll report the before/after benchmark and include regression coverage for any refactored behavior. Please assign it to me if it is still available.
AI disclosure: I used an AI coding assistant to help inspect the issue and draft this implementation plan.
Update after checking current develop: the referenced createAndFinishSpanForOtelSpan implementation and packages/opentelemetry/src/spanExporter.ts were removed by #22557, merged on 2026-07-27, together with SentrySpanProcessor/SentryExporter. There is no longer a benchmark or optimization target on the active branch, so I am withdrawing my claim. This issue appears safe to close as obsolete.
Activity
tahakotil commentedon Aug 29, 2026
I'd like to take this. I'll first add a focused benchmark around
createAndFinishSpanForOtelSpan, profile its hot allocations/calls, then make the smallest change that preserves span timestamps, status, attributes, links, and parent relationships. I'll report the before/after benchmark and include regression coverage for any refactored behavior. Please assign it to me if it is still available.AI disclosure: I used an AI coding assistant to help inspect the issue and draft this implementation plan.
tahakotil commentedon Aug 29, 2026
Update after checking current
develop: the referencedcreateAndFinishSpanForOtelSpanimplementation andpackages/opentelemetry/src/spanExporter.tswere removed by #22557, merged on 2026-07-27, together withSentrySpanProcessor/SentryExporter. There is no longer a benchmark or optimization target on the active branch, so I am withdrawing my claim. This issue appears safe to close as obsolete.s1gr1d commentedon Aug 31, 2026
Closing this issue, as those functions don't exist anymore in
v11.