Debounce changes to search input

[twjacobsen]

Bug description:

Not a bug per se, more a feature request/performance optimization suggestion.

With large lists, searching is a pain (initial rendering is "ok" - not good, though).

But searching a list of ~800 objects, using 2 properties and the or-filter from one of the examples is a pain, even on my quad-code i7. And it's practically impossible on older machines.

I suspect, that it's because the input is not properly debounced, so that 4 keystrokes results in 4 filterings, and 4 total refreshes of the ng-repeat.

I've looked at the source, but could not find the entry point where the search input is updating the data.

Also, looking at some performance tools, I see that a lot of time is used on parsing (using resultParser.source or the result of $parse), which is very expensive. Is it not possible to avoid this? I see it in all the formatters, why is something like ctrl.items not just used there?

[user378230]

Maybe you could submit a PR with the proposed performance improvements you've identified?

Thanks! 😃

[stibay]

It works just adding debouncing through the ng-model-options. F.ex ng-model-options="{ debounce: 500 }"

https://docs.angularjs.org/api/ng/directive/ngModelOptions