Joberto, looking at your plunker you are getting an error in your console. $timeout is undefined which means you didn't inject it in your directive. I assume since you passed a 'zero' delay you want to trigger immediate execution by the browser. So that's not working and maybe a cause for the lengthy execution. Beyond that, please summarize in plain English WHAT you want to do and HOW you want to do this in AngularJS. Perhaps you'll get more help. For example, we regularly retrieve large amounts remote date ($ajax) and have multiple ng-repeats with complex embedded directives and associated 1 & 2 way data bindings and the performance is absolutely fine. It's very simple to do.
Mo On Thursday, June 25, 2015 at 8:38:35 AM UTC-4, Joberto Diniz wrote: > > Well.. in my actual page I did not see any gain from using 1.3.16.. that's > a bummer :( > > On Thursday, June 25, 2015 at 2:40:46 AM UTC-3, Sander Elias wrote: >> >> Hi Joberto, >> >> I just checked, but on my computer, your time had dropped from almost 7 >> to almost 3 seconds, that's a performance gain of way over 50%! >> It takes some time to render and calculate every cell, you have to do >> that anyway. The only way to speed this up, is make an directive that takes >> the data for the cell, and build the HTML by hand, without any bindings in >> it. That way the number of bindings for each cell drop to 1. If that's not >> enough, you can do the same for each row. >> However, this is a bit more complex then letting angular doing the heavy >> lifting. >> >> Regards >> Sander >> > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
