-
Notifications
You must be signed in to change notification settings - Fork 25k
Improve profiling information for timers #45091
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
Conversation
|
This pull request was exported from Phabricator. Differential Revision: D58832112 |
|
This pull request was exported from Phabricator. Differential Revision: D58832112 |
Summary: Pull Request resolved: facebook#45091 Changelog: [internal] We're currently logging when we execute timers in Systrace/Perfetto, but we have no information about them whatsoever. This adds some additional information: * What kind of timer it is * It's ID * And most importantly, when it was created (including the ID as well). This allows us to know where was a specific timer scheduled and with what API. Differential Revision: D58832112
cb5e7e2 to
a0df93c
Compare
|
This pull request was exported from Phabricator. Differential Revision: D58832112 |
Summary: Pull Request resolved: facebook#45091 Changelog: [internal] We're currently logging when we execute timers in Systrace/Perfetto, but we have no information about them whatsoever. This adds some additional information: * What kind of timer it is * It's ID * And most importantly, when it was created (including the ID as well). This allows us to know where was a specific timer scheduled and with what API. Differential Revision: D58832112
a0df93c to
3fe6742
Compare
Base commit: 3dcf86b |
…using microtasks Differential Revision: D58816582
|
This pull request was exported from Phabricator. Differential Revision: D58832112 |
Summary: Pull Request resolved: facebook#45091 Changelog: [internal] We're currently logging when we execute timers in Systrace/Perfetto, but we have no information about them whatsoever. This adds some additional information: * What kind of timer it is * It's ID * And most importantly, when it was created (including the ID as well). This allows us to know where was a specific timer scheduled and with what API. Reviewed By: bgirard Differential Revision: D58832112
3fe6742 to
5b64db5
Compare
Summary: Pull Request resolved: facebook#45091 Changelog: [internal] We're currently logging when we execute timers in Systrace/Perfetto, but we have no information about them whatsoever. This adds some additional information: * What kind of timer it is * It's ID * And most importantly, when it was created (including the ID as well). This allows us to know where was a specific timer scheduled and with what API. Reviewed By: bgirard Differential Revision: D58832112
|
This pull request was exported from Phabricator. Differential Revision: D58832112 |
5b64db5 to
07449f7
Compare
|
This pull request has been merged in a8a76f9. |
Summary:
Changelog: [internal]
We're currently logging when we execute timers in Systrace/Perfetto, but we have no information about them whatsoever.
This adds some additional information:
This allows us to know where was a specific timer scheduled and with what API.
Differential Revision: D58832112