it'll negatively impact the desired goal of low latency new index readers?
- yes, i think so, thats the reason because i dont understand the
wiki-article ...
i set the warmupCount to 500 and i got no error messages, that solr isnt
available ...
but solr-stats.jsp show me a warmuptime of
okay, not the time ... the items ...
-
--- System
One Server, 12 GB RAM, 2 Solr Instances, 7 Cores,
1 Core with 31 Million Documents other Cores 100.000
- Solr1 for Search-Requests - commit every Minute - 5GB Xmx
-
- yes, i think so, thats the reason because i dont understand the
wiki-article ...
Maybe the article is out of date? I think it's grossly inefficient to
warm the searchers at all in the NRT case. Queries are being
performed across *all* segments, even though there should only be 1
that's new
Maybe the article is out of date?
- maybe .. i dont know
in my case it make no sense and i use another configuration ...
-
--- System
One Server, 12 GB RAM, 2 Solr Instances, 7 Cores,
1 Core with 31 Million Documents
make it sense to update solr for getting SOLR-571 ???
-
--- System
One Server, 12 GB RAM, 2 Solr Instances, 7 Cores,
1 Core with 31 Million Documents other Cores 100.000
- Solr1 for Search-Requests - commit every Minute
I think it's best to turn the warmupCount to zero because usually
there isn't time in between the creation of a new searcher to run the
warmup queries, eg, it'll negatively impact the desired goal of low
latency new index readers?
On Wed, Mar 9, 2011 at 3:41 AM, stockii stock.jo...@googlemail.com
