Here is my config now:
And my initial heap allocation is now set to 4 GB and a max of 8GB as per
Shawn's recommendation.
Thanks Jack, Walter and Shawn for your suggestions.
I will post the results on this forum for others to
Jack,
No. It is a simple search. I cannot limit what the search will be like. Like
I mentioned to Walter, search could land for a "*@gmail.com" or a "*yahoo*".
Most of the time it is the dreaded and expensive "contains" search.
Regards,
Giri
--
View this message in context:
http://lucene.472066
Hello Wunder,
I see your point. Will this help if I search for "giri", "giri@",
"giri@gmail", "@gmail.com" and other combinations.
So, if I use a StandardTokenizer, I will get the ALPHANUM without the "@"
and the '.'. So my phrases would be "giri","gmail","com". And I should do a
phrase search on t
Thanks Jack. The search is slow only when it is issued for the first time.
Ex. querying for *@gmail* takes 20+ seconds for the first time; when I
re-issue the same search, then it returns pretty quick(Possibly reading out
of cache).
But when I issue a new search *@yahoo.* then this too takes abou
Hello,
I have over 40 million records/documents and I need to retrieve them using
wildcard searches on email and / or firstname and / or lastname.
The firstname, lastname and blank search (*:*) all return results within 3
seconds. But my Email search alone takes more than 20-25 secs.
I would like
