7GB index taking forever to return hits

	Van Nguyen
	Aug 15, 2006 at 8:00 pm

United Rentals
Consider it done.™
800-UR-RENTS
unitedrentals.com

Search Discussions

Rob Staveley (Tom): Sounds like you want to tokenise CONTENTS, if you are not already doing so. Then you could simply have: +CONTENTS:white +CONTENTS:hard +CONTENTS:hat -----Original Message----- From: Van Nguyen Sent: 15 August 2006 01:30 To: java-user@lucene.apache.org Subject: RE: 7GB index taking forever to return hits It was how I was implementing the search. I am using a boolean query. Prior to the 7GB index, I was searching over a 150MB index that consist of a very small part of the bigger index. I was able

Follow ups

Van Nguyen: United Rentals Consider it done.™ 800-UR-RENTS unitedrentals.com
Chris Hostetter: : I'm now using a filter on the wildcard portion of the query. Takes 10s : to return results. I took out the wildcard query and just search on : terms and that takes 187ms to return the same results (well... Not : same... But a lot faster to return results). Unfortunately, the : wildcard query is part of the requirement. I'll play around with the : filter to see if I can reduce the search time. If i'm reading between the lines correctly, you have a requirement that every search be a "substring"
Erick Erickson: Three things come to mind: 1> You can think about caching your filters. This only makes sense if you have a fairly small number of wildcards that you *expect*. Probably not really viable, but I thought I'd mention it. 2> You say that the search is "part of the requirements". It might be worth asking the people who wrote the requirements why. I've sometimes found that requirements aren't cast in stone, and things get in there that would be "nice" to have, but when informed of the trade-offs, the

Discussion Navigation

view	thread \| post
posts	‹ prev \| 7 of 10 \| next ›

Discussion Overview

font	variable	Hotkey: f
user style	avatars	Hotkey: a