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
That is a good start. Use the Analysis page in the admin UI to see what the
tokenizer does.
wunder
On Mar 1, 2013, at 11:02 AM, girish.gopal wrote:
> Hello Wunder,
> I see your point. Will this help if I search for "giri", "giri@",
> "giri@gmail", "@gmail.com" and other combinations.
> So, if
On 3/1/2013 11:49 AM, girish.gopal wrote:
My Specs are:
Windows Server 2008 64 bit Dual Quad Core CPUs with 64 GB of RAM.
I have allocated 55GB of memory to Tomcat in its config.
In addition to the advice you've gotten about wildcards, your memory
allocation needs some tweaking. It is highly
It sounds like you have enough raw memory. How big is the index (GB)?
Are you doing anything like ngrams that generate zillions of terms?
-- Jack Krupansky
-Original Message-
From: girish.gopal
Sent: Friday, March 01, 2013 1:49 PM
To: solr-user@lucene.apache.org
Subject: Re: Email
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
Don't use wildcards. A leading wildcard matches against every token in the
index. This is the search equivalent of a full table scan in a relational
database.
Instead, create a field type that tokenizes e-mail addresses into pieces, then
use phrase search against that.
The address "f...@yahoo.
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
Make sure you have enough heap space for your JVM and the most if not all of
your index fits in OS system memory.
After you start Solr and issue a couple of queries, how much JVM heap is
available?
-- Jack Krupansky
-Original Message-
From: girish.gopal
Sent: Friday, March 01, 2013
