open-telemetry / open-telemetry/opentelemetry-lambda
Slow start-up?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 432
- Forks
- 246
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 47
Description
I tried out migrating away from AWS's X-Ray SDK for Lambda, but the Open Telemetry Lambda layer appears to add a significant amount to cold start time, which I didn't expect.
It was suggested I cross post, since this is actually the repo with the layers in.
https://github.com/aws-observability/aws-otel-lambda/issues/228#issuecomment-1193215390
Here's the data for reference:
I don't see any documentation on performance, comparison to X-Ray performance etc.
Is there a plan to reduce this? I didn't expect to have to add a Lambda layer to get OpenTelemetry working, I thought it would be included in the Lambda runtime as a first class thing, rather than being a sort-of add-on.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start with the cold-start measurements in this issue and the linked AWS X-Ray discussion, then identify which Lambda layer implementation and runtime are involved. Done would require a defined performance target, a reproducible comparison with X-Ray, and an agreed reduction or documentation plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, observability-sre, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100