-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
profiling(cocoa): add note about stopping launch profiler #13871
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
base: master
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Bundle ReportChanges will decrease total bundle size by 15 bytes (-0.0%) ⬇️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-server-cjsAssets Changed:
view changes for bundle: sentry-docs-client-array-pushAssets Changed:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, left one comment for potential improvement.
@@ -130,6 +130,10 @@ If configured with trace lifecycle, app start profiles are attached to a special | |||
|
|||
Every time `SentrySDK.startWithOptions` is called with app start profiling configured, a separate sample decision is generated with `sessionSampleRate` and stored until the next app launch (as well as `tracesSampleRate` if trace profile lifecycle is configured). The same sample decision will apply for the remainder of the profile session following that subsequent launch. | |||
|
|||
<Alert> | |||
If the SDK does not start on the same launch as a launch profiler is running, the profiler will run for the duration of that user session. Ensure proper configuration if you selectively start the Sentry SDK along with launch profiling. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
m
: Maybe we should explain here what "proper configuration" means.
@@ -130,6 +130,10 @@ If configured with trace lifecycle, app start profiles are attached to a special | |||
|
|||
Every time `SentrySDK.startWithOptions` is called with app start profiling configured, a separate sample decision is generated with `sessionSampleRate` and stored until the next app launch (as well as `tracesSampleRate` if trace profile lifecycle is configured). The same sample decision will apply for the remainder of the profile session following that subsequent launch. | |||
|
|||
<Alert> | |||
If the SDK does not start on the same launch as a launch profiler is running, the profiler will run for the duration of that user session. Ensure proper configuration if you selectively start the Sentry SDK along with launch profiling. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the SDK does not start on the same launch as a launch profiler is running, the profiler will run for the duration of that user session.
I'm having a little bit of trouble parsing this first sentence. Can you clarify a little bit? Would something like "...the same launch as the one where the profiler is running" make sense?
DESCRIBE YOUR PR
As noted here: getsentry/sentry-cocoa#3637 (comment)
We have a limitation where we cannot control what happens to a launch profiler if the SDK is never started after a profiled app launch.
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
LEGAL BOILERPLATE
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
EXTRA RESOURCES