Delay before search - performance issue

[dornstein]

I have lists with 10K+items and people are complaining that with each character they type there is a delay of a couple of seconds before the search completes. So typing ori (when searching for something like origin) take a long time because first chosen searches for o and then or and then ori, etc.

My first reaction is that chosen need a configurable option to be able to indicate how long of a delay after the last keystroke the search should start. Has there been discussion about this type of idea in the past? Are there any suggestions about this problem or simpler alternatives?

[KaraAJC]

I was just informed of Ajax-Chosen gem, however, it is a few years old, and it's not built by harvest...

[koenpunt]

A delay, or requiring a minimum amount of characters to be typed before filtering occurs would be useful options, I agree

_{Sent with GitHawk}

[dhwang]

+1