Thx. I will let you know the latest status.
>From: Lance Norskog
>Reply-To: solr-user@lucene.apache.org
>To: solr-user@lucene.apache.org, newsam
>Subject: Re: Re:The search response time is too loong
>Date: Tue, 28 Sep 2010 13:34:53 -0700
>
>Copy the index. Delete half of th
veral shards from the existing 8G index file, such as
> 4G per shards. Is there any tool to generate two shards from one 8G index
> file?
>
>>From: kenf_nc
>>Reply-To: solr-user@lucene.apache.org
>>To: solr-user@lucene.apache.org
>>Subject: Re: Re:The search respon
ply-To: solr-user@lucene.apache.org
>To: solr-user@lucene.apache.org
>Subject: Re: Re:The search response time is too loong
>Date: Mon, 27 Sep 2010 05:37:25 -0700 (PDT)
>
>
>"mem usage is over 400M", do you mean Tomcat mem size? If you don't give your
>cache si
Also, how many rows are you requesting at one time? I've seen cases where
the query time is blazing fast and the response writing is terribly slow
because of too many documents being sent in the response.
On Mon, Sep 27, 2010 at 6:37 AM, kenf_nc wrote:
>
> "mem usage is over 400M", do you mean T
"mem usage is over 400M", do you mean Tomcat mem size? If you don't give your
cache sizes enough room to grow you will choke the performance. You should
adjust your Tomcat settings to let the cache grow to at least 1GB or better
would be 2GB. You may also want to look into
http://wiki.apache.org/
We used SOLR 1.4. All queries were excuted in SOLR back-end. I guess that I/O
operations consume the time too much.
>From: "newsam"
>Reply-To: solr-user@lucene.apache.org"newsam"
>To: solr-user@lucene.apache.org
>Subject: Re:The search response time is too loo
