You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The profiler would be accessible via dev tools. When a developer installs the profiler DI module they get access to global functions they could invoke directly from the dev tools console.
The profiler would be exposed under global namespace ng (which in the future could host more tools). To profile change detection specifically, a developer would enter:
ng.profileChangeDetection();
The profiler would invoke LifeCycle.tick() at least 5 times and for at least 500ms. It will then compute the average and the standard deviation of amount of time it took to execute a single tick.
profileChangeDetection takes an optional named boolean parameter record that's false by default. When set to true, it records the profile as a CPU profile that could be inspected later in the "Profiles" tab of the dev tools:
ng.profileChangeDetection({record: true});
In the future, we may add more options as named parameters, such as custom number of tick runs or custom length of profile.
Activity
0x-r4bbit commentedon Aug 30, 2015
I love this. Same APIs could be used to make a decent browser extension out of it (or extending Batarang)
mhevery commentedon Aug 31, 2015
@yjbanov Sounds good to me. Please use
ngas the global object as it will be consistent withng.probeetc...gkalpak commentedon Sep 9, 2015
@yjbanov, shouldn't this have been closed by 8dd6c46 ?
yjbanov commentedon Sep 9, 2015
@gkalpak yep
angular-automatic-lock-bot commentedon Sep 7, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.