@mbrt wrote:
Hi Everybody,
I have just a quick question regarding the importance of the 2.000 watchers threshold with regards to the performance of an Angular.JS APP. Maybe it is completely obvious but I just can't get my head around it.
In the Ionic Documentation it reads:
Views are cached to improve performance. When a view is navigated away from, its element is left in the DOM, and its scope is disconnected from the $watch cycle. When navigating to a view that is already cached, its scope is reconnected, and the existing element, which was left in the DOM, becomes active again.
Does that mean that the 2.000 watcher limit applies only to the currently active view because it is not important if we have 4.000 watchers in two other non-active views since they are disconnected from the $watch cycle anyway and thus are not monitored?
And what would happen if we decided to disable the functionality to cache views? Would the watcher limit then be applied to all views (active and non-active) since they would not be disconnected from the watch cycle any more?
Thanks and regards, Matthias
Posts: 1
Participants: 1