Hi Tomas,
I give you other details.
- The fragment field contains 3KB xml messages.
- The queries that I used for the test are (I only change the word to
search inside the fragment field between requests): curl "
http://localhost:8983/solr/sepa/select?q=+fragment%3A*A*+&fq=marked%3AT
Hi Shawn,
I expect that indexing is a little bit slower with replication but in my
case is 3 times worst. I don't explain this.
The monitored consumption of resources is:
All the test have point out an I/O utilization of 100MB/s during
loading data on disk cache, disk cache utilizatio
Hi Luca,
It looks like your queries are complex wildcard queries. My theory is that
you are CPU-bounded, for a single query one CPU core for each shard will be
at 100% for the duration of the sub-query. Smaller shards make these
sub-queries faster which is why 16 shards is better than 8 in your cas
On 1/8/2016 7:55 AM, Luca Quarello wrote:
> I used solr5.3.1 and I sincerely expected response times with replica
> configuration near to response times without replica configuration.
>
> Do you agree with me?
>
> I read here
> http://lucene.472066.n3.nabble.com/Solr-Cloud-Query-Scaling-td4110516
Hi Matteo,
the questions are two:
- "Why are response times on a solr cloud collecton with 1 replica
higher than on solr cloud without replica"
Configuration1: solrCloud with two 8 cores VMs each with 8
shards of 17M docs
Configuration2: solrClous with two 8 cores VMs
Hi Erick,
I used solr5.3.1 and I sincerely expected response times with replica
configuration near to response times without replica configuration.
Do you agree with me?
I read here
http://lucene.472066.n3.nabble.com/Solr-Cloud-Query-Scaling-td4110516.html that
"Queries do not need to be routed
Hi Erick,
I used solr5.3.1 and I sincerely expected response times with replica
configuration near to response times without replica configuration.
Do you agree with me?
I read here
http://lucene.472066.n3.nabble.com/Solr-Cloud-Query-Scaling-td4110516.html
that "Queries do not need to be routed
What version of Solr? Prior to 5.2 the replicas were doing lots of
unnecessary work/being blocked, see:
https://lucidworks.com/blog/2015/06/10/indexing-performance-solr-5-2-now-twice-fast/
Best,
Erick
On Tue, Jan 5, 2016 at 6:09 AM, Matteo Grolla wrote:
> Hi Luca,
> not sure if I understoo
Hi Luca,
not sure if I understood well. Your question is
"Why are index times on a solr cloud collecton with 2 replicas higher than
on solr cloud with 1 replica" right?
Well with 2 replicas all docs have to be deparately indexed in 2 places and
solr has to confirm that both indexing went well
Hi,
I have an 260M documents index (90GB) with this structure:
where the fragmetnt field contains XML messagges.
There is a search function that provide the messagges satisfying a search
criterion.
TARGET:
To find the best c
10 matches
Mail list logo
