*sleep 1.5 seconds* command per file
...FWIW I found in trying to cfindex 35K documents that if I did a
cfdirectory list and added a delay per file indexed (and a cfsetting with a
REALLY long timeout), CPU use dropped from 58% to ~19% and I got much
farther without the dread maxWarmingSearchers=4 e
oooh. my queryResultCache has a warmupTime from 54000 => ~1 Minute
any suggestions ??
-
--- System
One Server, 12 GB RAM, 2 Solr Instances, 7 Cores,
1 Core with 31 Million Documents other Cores < 100.000
- Solr1 for Sea
my filterCache has a warmupTime from ~6000 ... but my config is like this:
LRU Cache(maxSize=3000, initialSize=50, autowarmCount=50 ...)
should i set maxSize to 50 or similar value ?
-
--- System
One Server, 12 GB RAM, 2 S
i start a commit on "searcher"-Core with:
.../core/update?commit=true&waitFlush=false
-
--- System
One Server, 12 GB RAM, 2 Solr Instances, 7 Cores,
1 Core with 31 Million Documents other Cores < 100.000
- Solr1 for Search
commited; there is no actual commit operation.
-Original Message-
From: Walter Underwood [mailto:wunderw...@netflix.com]
Sent: Thursday, December 11, 2008 11:45 AM
To: solr-user@lucene.apache.org
Subject: Re: exceeded limit of maxWarmingSearchers=4
It sounds like you need real-time search
Also, if you are using solr 1.3, solr 1.4 will reopen readers rather
than open them again. This means only changed segments have to be
reloaded. If you turn off all the caches and use a bit higher merge
factor, maybe a low max merge docs, you can prob get things a lot
quicker. There will still
It sounds like you need real-time search, where documents are
available in the next query. Solr doesn't do that.
That is a pretty rare feature and must be designed in at the start.
The usual workaround is to have a main index plus a small delta
index and search both. Deletes have to be handled se
will not be part of the
query results.
> Date: Thu, 11 Dec 2008 14:09:47 -0500
> From: markrmil...@gmail.com
> To: solr-user@lucene.apache.org
> Subject: Re: exceeded limit of maxWarmingSearchers=4
>
> chip correra wrote:
> > We’re using Solr as a backend indexe
chip correra wrote:
We’re using Solr as a backend indexer/search engine to support an AJAX
based consumer application. Basically, when users of our system create
“Documents” in our product, we commit right away, because we want to
immediately re-query and get counts back from Solr to
