Big array slows things to a halt

[justgoscha]

Big array slows things to a halt

[j0an]

+1

[davidmh]

I think there's another way to look at the problem. Maybe trying to read that many items at the same time, to just show 10 of them, it's a bit of unnecessary processing.

Let's remember the basic autocomplete functionality:

1. The user writes a query on the search box
2. The service (an ajax request for data, through the on-type function) responds with the top 10 or 20 most relevant options.
3. If those options are not the ones the user is looking for, he can keep writing to narrow the results.

Getting only the items you actually need seems like the way to go, booth for the client and the server side.

I think for this particular case, the limit should come from the server, or the equivalent source you are using.

---

Edit: I just realised that maybe I'm not seeing the entire picture on your case, could you give us some context?

[davidmh]

I'm closing since I don't think that issue it's related to the functionality of this directive.

If you can provide us with a justifiable example, please reopen this issue.

[JustGoscha]

You could also use something like bindonce (https://github.com/Pasvaz/bindonce) if you want to show all the results.

Or customize the template to do what you want.