Debug change detection appears to run when prodmode is called

[escardin]

Steps to reproduce and a minimal demo of the problem
http://plnkr.co/edit/oOsWYXMeXMq7nPzBLETH?p=preview
In the console, the same number of change detection calls shows up whether prodmode is enabled or not.
What steps should we try in your demo to see the problem?
Enable/disable prod mode and compare change calls in the console.

Current behavior
As many change detection cycles as when in debug mode.

Expected/desired behavior
Approximately half as many change detection cycles.

Other information
Totally not sure if I've reproduced this correctly.

[sandlunds]

I can add that it didn't seem to be this way back in beta 17. IE 11 got a huge speedboost by enabling prodmode but it doesn't have any effect anymore as far as I can see.

[jhades]

I just noticed the same while profiling an angular universal app. The app is in production mode (100% sure), no enableProd Mode warning shows. And we can see that the DebugAppView is present at multiple places in the component tree, for a run in production mode:

cc @gdi2290

[shaharvaldman]

We're experiencing the same behavior.
It is very difficult to analyze the performance of an angular2 application (especially the change-detection cycle) when the app appears (?) to spend so much time on Debug mode, even though we tried to disable it.
Is the production-mode not ready yet, or is this the expected behavior in production?

[tbosch]

See #9295 for a workaround. Will fix this ASAP.
Closing this issue to track in #9295.