Thanks a lot!
you mean i have to increase the resources.
1.Can the distributed search improve the speed.?
2.I have read from some thread that spellchecker takes time.Is spellchecker
is one of the curlprit for more response time?
On Tue, Dec 21, 2010 at 10:20 PM, Shawn Heisey-4 [via Lucene] <
ml
On 12/21/2010 3:02 AM, Anurag wrote:
I am using spellchecker in the query part. Now my search time has become
more. say initiallly it was 1000ms now its 3000ms.I have data index of size
9GB.
My query http://localhost:8983/solr/spellCheckCompRH/?q=
http://localhost:8983/solr/spellCheckCompRH/?q="+
I am using spellchecker in the query part. Now my search time has become
more. say initiallly it was 1000ms now its 3000ms.I have data index of size
9GB.
My query http://localhost:8983/solr/spellCheckCompRH/?q=
http://localhost:8983/solr/spellCheckCompRH/?q="+search+"&spellcheck=true&fl=spellchec
It is crucial to MEASURE your system to confirm your bottleneck.
I agree that you are very likely to be disk I/O bound with such little
memory left for the OS, a large index and many terms in each query.
Have your IT guys do some monitoring on your disks and log this while
under load. Then you sho
Thanks for your input guys. I will surely try these suggestions, in
particular, reducing heap size JAVA_OPTION and adjusting cache sizes to see
if that makes a difference.
I am also considering upgrading RAM for slave nodes, and also looking into
moving from SATA enterprise HDD to SSD flash/DRAM
More on this: you should give Solr enough memory to run comfortably,
then stop. Leave as much as you can for the OS to manage its disk
cache. The OS is better at this than Solr is. Also, it does not have
to do garbage collection.
Filter queries are a big help. You should create a set of your basic
Most of your time is spent doing the query itself, which in the light
of other information provided, does not surprise me. With 12GB of RAM
and 9GB dedicated to the java heap, the available RAM for disk caching
is pretty low, especially if Solr is actually using all 9GB.
Since your index is
First, thanks very much for a prompt reply. Here is more info:
===
a) What operating system?
Debian GNU/Linux 5.0
b) What Java container (Tomcat/Jetty)
Jetty
c) What JAVA_OPTIONS? I.e. memory, garbage collection etc.
-Xmx9000m -DDEBUG -Djava.awt.headless=true
-Dorg.mortbay.
On Wed, 18 Aug 2010 05:18:34 -0700 (PDT)
Muneeb Ali wrote:
>
> Hi All,
>
> I need some guidance over improving search response time for our
> catalog search.
[...]
> I would appreciate if anyone with similar background could shed
> some light on upgrading hardware in our situation. Or if any
>
Some questions:
a) What operating system?
b) What Java container (Tomcat/Jetty)
c) What JAVA_OPTIONS? I.e. memory, garbage collection etc.
d) Example queries? I.e. what features, how many facets, sort fields etc
e) How do you load balance queries between the slaves?
f) What is your search latency
10 matches
Mail list logo
