Hi All, Inspired by this thread I took plunker and created a small sample <http://plnkr.co/edit/nuN0qBgiOQzjdbzddsIi?p=preview>. In there, you can play around with whatever you think is a huge amount of data. It will generate any amount you see fit. On my computer, everything works snappy until I hit 2.000 rows (10.000+ watchers). It is workable up until 6.000 rows. Although sorting the table then is taking a bit longer than I would like, and the first few letters in search are then sluggish. There is intentional NO optimization done. In real practice, never do it like this. If you would put a limitTo on the repeat, everything works fine untill you run out of resources. tested that up until 12.500 rows.. everything works snappy then.
So if you make a good UX (in this case, use at least paging and/or limit the number of visible row) the number of watches will seldom be much of an issue. 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 https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
