-
Notifications
You must be signed in to change notification settings - Fork 25.2k
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
redundant (?) debug info in production mode #9208
Comments
Might be related to #8508 but hard to tell. Your post doesn't contain a lot of information. |
I'm working on making this configurable |
vicb
added a commit
to vicb/angular
that referenced
this issue
Jun 16, 2016
vicb
added a commit
to vicb/angular
that referenced
this issue
Jun 16, 2016
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We are currently evaluating the performance of our application after upgrading it to angular2.
Naturally, one of the areas we are looking into is the elapse time of the change detection cycle. Unfortunately, the execution time is longer than we expected.
Analysis shows that even when running in production mode, a large portion of the time is spent on self.debug functions of the change detection generated objects.
Example:
_View_xxx.prototype.detectChangesInternal = function(throwOnChange) {
...
self.debug(0,1,37);
...
}
Are these debug statements expected to be removed from the source in production mode on a later RC?
Thanks
The text was updated successfully, but these errors were encountered: