demo page freezes when you land on it about angulardart.org HOT 10 OPEN

@naomiblack I've noticed this too.

from angulardart.org.

Seems to be related to the Backend App. IMHO, for now, a simple fix would be to limit the number of entries in the DB to some small number (say 50 or 100).

from angulardart.org.

Or tweak the demo app to fetch only the last 50 or 100 entries.

from angulardart.org.

AngularFire is loading data in a very inefficient manner: it listens to child_added event and adds children one by one to the collection. This causes n^2 behavior when loading initial state because on each added children we redigest, detect a new child and update ng-repeat. n is rather large which causes 10s pause. (There are other n^2 things in there but redigesting and updating ng-repeat over and over again is the biggest offender).

Instead of doing this AngularFire should seed initial state of the collection using value event and ignore child_added when child is already present.

I hacked it together out of curiosity and while it does not remove pause altogether it does reduce it considerably. I can send a pull request against AngularFire.

/cc @mhevery

from angulardart.org.

@mraleph Do send in your pull request if you already have one to https://github.com/firebase/angularFire. An easy way to avoid redigesting on the initial value load is doing the following:

var initialLoaded = false;
ref.on('child_added', function(snapshot) {
  if (!initialLoaded) return;
  // otherwise, add to collection
});
ref.once('value', function(snapshot) {
  initialLoaded = true;
  // set collection to snapshot.val();
});

from angulardart.org.

Hope to see a fix work its way to the AngularDart demo page soon. It gives the impression that AngularDart and even Dart is not ready for evaluation let alone production.

from angulardart.org.

Actually this issue on the demo page was the main reason for me not to look any further on AngularDart. If the main AngularDart devs do not get their simple demo good running why should I invest time in learning something which is not ready yet and only looks good at first glance. Currently I'm more looking into Angular.JS.

from angulardart.org.

We've temporarily fixed the issue by clearing the entries in Firebase. Will get a more substantive fix in soon, but the team's focus right now is on getting 1.0 launched. Please let me know if it's still molasses slow to load.

from angulardart.org.

It's much faster for me now. Do we need to periodically clear the Firebase entries until we really fix this?

from angulardart.org.

FirebaseExtended/angularfire#304 should help with this. The 0.8 release batches elements and only runs one compile per batch. The wait time can be adjusted for maximum efficiency.

from angulardart.org.