How to stop digest cycle manually in angularjs

All we need is an easy explanation of the problem, so here it is.

As digest cycle do the dirty checking of the variable that is if there are 100 scope variables and if I change one variable then it will run watch of all the variables.

Suppose I have 100 scope model variables that are independent of each other. If I make changes in one variable then I don’t want to check all other 99 variables. Is there any way to do this ? If yes, how ?

How to solve :

I know you bored from this bug, So we are here to help you! Take a deep breath and look at the explanation of your problem. We have many solutions to this problem, But we recommend you to use the first method because it is tested & true method that will 100% work for you.

Method 1

Surprisingly, this is usually not a problem, Browsers don’t have problems even with thousands of bindings, unless the expressions are complex. The common answer for how many watchers are ok to have is 2000.

Solutions :

It is fairly easy onwards from AngularJS 1.3, since one-time bindings are in core now.

  1. One time Binding of the variables.

We can use One time binding(::) directive to prevent the watcher to watch the unwanted variables. Here, variable will be watch only once & after that it will not update that variable.

  1. Stop the digest cycle manually.


<ul ng-controller="myCtrl">
  <li ng-repeat="item in Lists">{{lots of bindings}}</li>

Controller Code :

app.controller('myCtrl', function ($scope, $element) {
  $element.on('scroll', function () {
    $scope.Lists = getVisibleElements();

During the $digest, you are only interested in changes to Lists object, not changes to individual items. Yet, Angular will still interrogate every single watcher for changes.

directive for stop and pause the digest:

app.directive('stopDigest', function () {
  return {
    link: function (scope) {
      var watchers;

      scope.$on('stop', function () {
        watchers = scope.$$watchers;
        scope.$$watchers = [];

      scope.$on('resume', function () {
        if (watchers)
          scope.$$watchers = watchers;

Now, Controller code should be changed :

<ul ng-controller="listCtrl">
  <li stop-digest ng-repeat="item in visibleList">{{lots of bindings}}</li>

app.controller('myCtrl', function ($scope, $element) {
  $element.on('scroll', function () {
    $scope.visibleList = getVisibleElements();


Reference Doc :


Method 2

This is a good question and highlights one of the biggest deficiencies with Angular 1.x. There is little control over how the digest cycle is managed. It is meant to be a black box and for larger applications, this can cause significant performance issues. There is no angular way of doing what you suggest, but There is something that would help you achieve the same goals (ie- better performance of the digest cycle when only one thing changes).

I recommend using the bind-notifier plugin. I have no relationship with the project, but I am using it for my own project and have had great success with it.

The idea behind is that you can specify certain bindings to only be $digested when a specific event has been raised.

There are multiple ways of using the plugin, but here is the one that I find must effective:

In a template file, specify a binding using the special bind-notifier syntax:


These two bindings will not be dirty-checked on most digest cycles unless they are notified.

In your controller, when user data changes, notify the bindings like this:

this.refreshUserData().then(() => {

(and similar for job-data-changed)

With this, the bindings for will only be checked on the broadcast.

A few things to keep in mind:

  1. This essentially subverts one of the key benefits of angular (also it’s core weakness for large applications). Two way binding usually means that you don’t need to actively manage changes to your model, but with this, you do. So, I would only recommend using this for the parts of your application that have lots of bindings and cause slowdowns.
  2. $emit and $broadcast themselves can affect performance, so try to only call them on small parts of the $scope tree (scopes with few or no children).
  3. Take a good look at the documentation since there are several ways to use the plugin. Choose the usage pattern that works best for your application.

Method 3

This is quite a specific use-case to do exclusive/conditional checks in the digest cycle and I don’t think it is possible without forking/hacking the angular core.

I would consider refactoring how/what you are $watching. Perhaps using ngModelController‘s $viewChangeListeners would be more suitable than $watch?

Note: Use and implement method 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from or, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply