Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question about performance with 500+ options #39

Open
sugaaloop opened this issue Apr 6, 2016 · 5 comments
Open

Question about performance with 500+ options #39

sugaaloop opened this issue Apr 6, 2016 · 5 comments
Labels

Comments

@sugaaloop
Copy link

I'm having performance issues when the option list is 500+ in size, any suggestions of how I could research improvements? Love the tool, by the way.

@Nishchit14
Copy link
Contributor

You can use remote option and fetch data on demand rather than loading all data first.

@sugaaloop
Copy link
Author

Thanks for the idea @Nishchit14, however, loading data is not the bottleneck. Creating the select, and I suppose the several ng-repeats, is where the slowdown occurs.

@indrimuska
Copy link
Owner

Yes @sugaaloop, I think so too, but I don't have the time to understand how to pack a fix to improve performances. If you have any idea or you are interested in contribution you're always be welcome! :)

@andreialecu
Copy link
Contributor

andreialecu commented Apr 14, 2016

You can still use the remote option and filter your options within it to only return a few of them that match the user input, instead of the huge list.

@jeeyyy
Copy link

jeeyyy commented Jan 29, 2018

This is fixed in a high performance variant/fork of the same component:
https://github.com/jkodu/angular-selector-on-steroids

Refer enhanced example page - https://jkodu.github.io/angular-selector-on-steroids/ (allow unsafe scripts).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants