Personally I'd recommend only returing only a small subset of the results from the backend. Rather than returning all 5000+ results needlessly (is anyone going to really look through them all or just keep filtering?). Limit the DB query to 100 or so. You'll need to set matchSubset = false though on the autocomplete object otherwise you autocomplete won't be accurate. I will say this depends on the type of results being returned from the back end, turning off matchSubset can have a performance hit if you have low network speeds etc as it will always make a call to the backend. Also maybe you should be filtering after more keystrokes - are you really gaining anything by filtering at three if the result sets are so large? Just my $0.02 James.
________________________________ From: jquery-en@googlegroups.com on behalf of Saumin Sent: Thu 29/01/2009 14:48 To: jQuery (English) Subject: [jQuery] Re: autocomplete plugin by bassistance - loading of huge number of records Hi Jörn Thanks for your quick response. Would you have some sample code to do that? It would be great if you can point me in a direction with respect to jquery.autocomplete.js. I appreciate it. Saumin On Jan 29, 3:28 am, Jörn Zaefferer <joern.zaeffe...@googlemail.com> wrote: > I recommend hard limiting the items loaded from the server, in > combination with scrolling. For example, load 100 items (should be > fast enough), but display only 10. The other 90 can be checked by > scrolling, while it is rather obvious that its easier to reduce the > list by typing more. > > Jörn > > > > On Wed, Jan 28, 2009 at 10:07 PM, Saumin <saumin.pa...@gmail.com> wrote: > > > hi, > > we are using theautocompleteplugin by bassistance.de. Our business > > people want the users to search database with half a million rows. We > > have minChars set as 3, but then also some combinations get around > > 5000 rows. In that case, the user has to wait for at least 20+ > > seconds. I know that the database query comes back with results in > > less than 1 second, but the function filllist() takes lot of time as > > there are lot of records. Is there anything somebody can suggest to > > make it load faster? If not, i wanted to introduce paging in this > > control. Has this been done? I would really appreciate a quick > > response. > > > Thanks!- Hide quoted text - > > - Show quoted text - -------------------------------------------------------------------- This e-mail is intended solely for the addressee and is strictly confidential; if you are not the addressee please destroy the message and all copies. Any opinion or information contained in this email or its attachments that does not relate to the business of Kainos is personal to the sender and is not given by or endorsed by Kainos. Kainos is the trading name of Kainos Software Limited, registered in Northern Ireland under company number: NI19370, having its registered offices at: Kainos House, 4-6 Upper Crescent, Belfast, BT7 1NT, Northern Ireland. Registered in the UK for VAT under number: 454598802 and registered in Ireland for VAT under number: 9950340E. This email has been scanned for all known viruses by MessageLabs but is not guaranteed to be virus free; further terms and conditions may be found on our website - www.kainos.com
