Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Handle App Start Continuous Profiling v8 (p4) #3730
Handle App Start Continuous Profiling v8 (p4) #3730
Changes from 1 commit
ffc470f
391485f
089f636
b7e889c
540e276
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
as I understood there could be only one profiler at a time (cont. or tx-based), right? Just got an idea we could have a general
IProfiler
interface (that would have all the methods thatIContinuousProfiler
currently has), and then it'd have a sub-interfaceITransactionProfiler
with the tx-specific methods.This way you could only manage one instance of
IProfiler
everywhere (like here) and it would be more readable I guess.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.
you're probably right on this, but in the long term we will deprecate and optionally remove the transaction profiler.
I think the extraction of the
AndroidProfiler
is enough for now.But we can refactor it if you have a strong preference