Well to be fair, this query is 30+ terms, and probably should just be turned into a SQL Call. I'll be implementing all of the suggestions, and see if I can't get the time down to a reasonable level.
-- Eric Marden Sr. PHP Developer -----Original Message----- From: Markus Fischer [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 5:00 PM To: Eric Marden Cc: [email protected] Subject: Re: [fw-general] Speeding up Lucene Are you using one of your queries already takes 23seconds with an index as small as 80kb? Eric Marden wrote: >> Do you have a lot of data in your index, essentially using the index > as a database replacement? > > 20 documents. Index is about 80kb or so. We are using it as DB > replacement, due to the fact that the production set up will have a > mysql cluster behind it (no FULLTEXT index available). However this > will grow when we reimport all of the production data into the new schema. > > > > -- > Eric Marden > > > -----Original Message----- > From: Kevin Schroeder [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 19, 2008 4:33 PM > To: Eric Marden; [email protected] > Subject: RE: [fw-general] Speeding up Lucene > > > > > > Kevin Schroeder > Technical Consultant > Zend Technologies, Ltd. > > www.zend.com > > > > > > > > >> -----Original Message----- >> From: Eric Marden [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, March 19, 2008 3:23 PM >> To: [email protected] >> Subject: RE: [fw-general] Speeding up Lucene >> >> P.S. - This is the only one of my search types that takes a long time. >> All the others can return the page in 3 seconds (timed with Yslow). >> This one is doing it in 23seconds. I've reduced other bottlenecks (it >> was plus 30seconds). >> >> >> >> -- >> Eric Marden > >
