Skip to content
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

feat: add profiler #2283

Merged
merged 5 commits into from
Nov 5, 2024
Merged

feat: add profiler #2283

merged 5 commits into from
Nov 5, 2024

Conversation

KishenKumarrrrr
Copy link
Contributor

Problem

This PR is a continuation of #2282 . The purpose of turning on profiling is for us to collect some concrete data on what the exact bottleneck is during callbacks so we don't succumb to premature optimisation.

There is a risk that turning this feature on in production would be detrimental to the application performance. As such, I am only doing so for 20% of all our servers.

@KishenKumarrrrr KishenKumarrrrr self-assigned this Nov 1, 2024
Copy link

@jwnicholas99 jwnicholas99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jwnicholas99
Copy link

As discussed in real life, the probability of >30 enabled profiling is 0.6%

image

Copy link
Member

@jia1 jia1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I don't see any breaking changes that apply to us (pertaining to dd-trace upgrade from v2 to v5). I also do not know of and cannot find a field/config inside tracer.init({ ... }) that directly configures the sampling rate for profiling, so this is great!

@KishenKumarrrrr KishenKumarrrrr merged commit 80e0090 into master Nov 5, 2024
7 checks passed
@KishenKumarrrrr KishenKumarrrrr deleted the feat/add-profiler branch November 5, 2024 01:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants