These are simple search queries and Its multithreaded .
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Index-linear-growth-Performance-degradation-tp4000934p4001184.html
Sent from the Solr - User mailing list archive at Nabble.com.
The queries were extracted from production log.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Index-linear-growth-Performance-degradation-tp4000934p4001182.html
Sent from the Solr - User mailing list archive at Nabble.com.
AM, feroz_kh wrote:
> Its 7,200,000 hits == number of documents found by all 10K queries.
> We have RHEL tikanga version.
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Solr-Index-linear-growth-Performance-degradation-tp4000934p4001069.html
Its 7,200,000 hits == number of documents found by all 10K queries.
We have RHEL tikanga version.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Index-linear-growth-Performance-degradation-tp4000934p4001069.html
Sent from the Solr - User mailing list archive at
Its 7.2Gig Hits. (GB was typo)
This is the total number of index hits - calculated by summing each
"numFound" attribute from solr query response.
We have RHEL Tikanga version.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Index-linear-growth-Performance-d
index hits == total number of documents found by search query.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Index-linear-growth-Performance-degradation-tp4000934p4001063.html
Sent from the Solr - User mailing list archive at Nabble.com.
It looks like reducing the jvm heap allocation did help in lowering the
response time to some extent.
Thanks for the pointer.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Index-linear-growth-Performance-degradation-tp4000934p4001056.html
Sent from the Solr - User
doesn't degrade a lot(i.e. almost doubling) when
> the index size is doubled ?
> Or we cannot do anything about it ?
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Solr-Index-linear-growth-Performance-degradation-tp4000934p4001034.html
&
a way that we can force or tune in such a way that the response
time remains constant or doesn't degrade a lot(i.e. almost doubling) when
the index size is doubled ?
Or we cannot do anything about it ?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Index-linear-gro
documents here
> Just testing the solr index search - i just the have the indexes.
> For 14GB index the RAM cache gets filled with 14 GB around
> For 28GB index the RAM cache gets filled with 28GB around
> The Document cache size is 200MB max and initial 20MB.
>
>
>
> --
&g
context:
http://lucene.472066.n3.nabble.com/Solr-Index-linear-growth-Performance-degradation-tp4000934p4001011.html
Sent from the Solr - User mailing list archive at Nabble.com.
our servers so that the performance isn't
> affected even when index size doubles or triples ?
>
>
>
>
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Solr-Index-linear-growth-Performance-degradation-tp4000934.html
> Sent from the Solr - User mailing list archive at Nabble.com.
--
Lance Norskog
goks...@gmail.com
.n3.nabble.com/Solr-Index-linear-growth-Performance-degradation-tp4000934.html
Sent from the Solr - User mailing list archive at Nabble.com.
13 matches
Mail list logo
