Skip to content

Context optimization for agent #4016

@trask

Description

@trask

In profiling, I'm seeing a good amount of time spent reading the (current) span and the SERVER span from the context.

It may be possible to optimize this by using a context implementation in the agent which has dedicated fields for (current) span and SERVER span.

I think this would be worth it, since we expect these two fields to be present most of the time.

I'm not sure if this would be enough (with special checking in get and with on the passed in key), of if we would further want to make Span and ServerSpan use the optimized Context directly somehow (not through generic get and with).

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions