I'm using Chosen in a term reference field; the vocabulary has more than 15,000 terms...
Chosen slows down a lot with many terms of taxonomy and the browser (Firefox, IE) crashes.

Comments

Taxoman’s picture

Taxoman commented
Title: Chosen slows down a lot when it is used with many terms of taxonomy » Significant performance drop when used on vocabularies with thousands of terms
Version: 7.x-1.0 » 7.x-2.x-dev
Component: User interface » Code
Category: bug » task

That's relatively unique, and possibly not exactly a bug.
Performance issues should be looked into though.

linus79’s picture

linus79 commented

I used Autocomplete deluxe, alternatively; it's more rapid.
Unfortunatly I can't use Autocomplete deluxe instead of Chosen becouse Autocomplete deluxe finds needless terms. Example: if you type "apple", it finds "apple" and "pineapple"; it should find only "apple".

hydra’s picture

hydra commented
Status: Active » Fixed

Well, with 15000 terms, this is a javascript issue and can't be solved by this module. Some kind of ajax autocompletion in chosen.js would be handy to get this right.
Did you take a look at the select2 fork of chosen? http://ivaynberg.github.io/select2/
It has a data load approach integrated which looks pretty promising for huge amount of tags. I would love to allow chosen forks as alternative libraries for the chosen module. Help is always welcome, have a look at #1705568: Consider to allow using forks of chosen
Also I would consider to open an issue in the project issue queue of chosen, perhaps they can help you more.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.