Re: How to trace one query？the debug/debugQuery info are not enough to find out why a query is slow

On 8/24/2018 5:17 AM, zhenyuan wei wrote: Thanks again~ @Shawn @Jan Høydahl What is the recommend size of one shard？or how many docs per shard is recommend? My collection has 20 shard，each shard is 30~50GB。 There are no general rules.  Every situation will be different, and advice that works f

Re: How to trace one query？the debug/debugQuery info are not enough to find out why a query is slow

Thanks again~ @Shawn @Jan Høydahl What is the recommend size of one shard？or how many docs per shard is recommend? My collection has 20 shard，each shard is 30~50GB。 @Shawn according to your wiki and e-mail reply， to achieve a better query performance ，I estimate the RAM requirement like follow： 7

Re: How to trace one query？the debug/debugQuery info are not enough to find out why a query is slow

Shawn, the block cache seems to be off-heap according to https://lucene.apache.org/solr/guide/7_4/running-solr-on-hdfs.html So you have 800G across 4 nodes, that gives 500M docs and 200G index data per solr node and 40G per sh

Re: How to trace one query？the debug/debugQuery info are not enough to find out why a query is slow

On 8/23/2018 5:19 AM, zhenyuan wei wrote: Thanks for your detail answer @Shawn Yes I run the query in SolrCloud mode, and my collection has 20 shards, each shard size is 30~50GB。 4 solr server, each solr JVM use 6GB, HDFS datanode are 4 too, each datanode JVM use 2.5GB。 Linux server host are 4

Re: How to trace one query？the debug/debugQuery info are not enough to find out why a query is slow

Thanks for your detail answer @Shawn Yes I run the query in SolrCloud mode, and my collection has 20 shards, each shard size is 30~50GB。 4 solr server, each solr JVM use 6GB, HDFS datanode are 4 too, each datanode JVM use 2.5GB。 Linux server host are 4 node too，each node is 16 core/32GB RAM/1600G

Re: How to trace one query？the debug/debugQuery info are not enough to find out why a query is slow

On 8/23/2018 4:03 AM, Shawn Heisey wrote: Configuring caches cannot speed up the first time a query runs.  That speeds up later runs.  To speed up the first time will require two things: 1) Ensuring that there is enough memory in the system for the operating system to effectively cache the in

Re: How to trace one query？the debug/debugQuery info are not enough to find out why a query is slow

On 8/23/2018 3:41 AM, zhenyuan wei wrote: Thank you very much to answer. @Jan Høydahl My query is simple, just wildcard last 2 char in this query（have more other query to optimize） curl " http://emr-worker-1:8983/solr/collection005/query?q=v10_s:YY*&rows=10&&fl=id&echoParams=a

Re: How to trace one query？the debug/debugQuery info are not enough to find out why a query is slow

he full list of query parameters in use, >> perhaps you spot something? >> If you start Solr with -v option then you get more verbose logging in >> solr.log which may help >> >> Can you share with us how your query looks like, including all parameters >> from the section with echoParams=all enabled? >> >> -- >> Jan Høydahl, search solution architect >> Cominvent AS - www.cominvent.com >> >> > 23. aug. 2018 kl. 11:09 skrev zhenyuan wei : >> > >> > Hi all， >> >I do care query performance, but do not know how to find out the >> reason >> > why a query so slow. >> > *How to trace one query？*the debug/debugQuery info are not enough to >> find >> > out why a query is slow。 >> > >> > >> > Thanks a lot~ >> >>

Re: How to trace one query？the debug/debugQuery info are not enough to find out why a query is slow

ing in > solr.log which may help > > Can you share with us how your query looks like, including all parameters > from the section with echoParams=all enabled? > > -- > Jan Høydahl, search solution architect > Cominvent AS - www.cominvent.com > > > 23. aug. 2018 kl. 11:09 skrev zhenyuan wei : > > > > Hi all， > >I do care query performance, but do not know how to find out the > reason > > why a query so slow. > > *How to trace one query？*the debug/debugQuery info are not enough to find > > out why a query is slow。 > > > > > > Thanks a lot~ > >

Re: How to trace one query？the debug/debugQuery info are not enough to find out why a query is slow

uan wei : > > Hi all， >I do care query performance, but do not know how to find out the reason > why a query so slow. > *How to trace one query？*the debug/debugQuery info are not enough to find > out why a query is slow。 > > > Thanks a lot~

How to trace one query？the debug/debugQuery info are not enough to find out why a query is slow

Hi all， I do care query performance, but do not know how to find out the reason why a query so slow. *How to trace one query？*the debug/debugQuery info are not enough to find out why a query is slow。 Thanks a lot~