Hi Shawn, Here is a screenshot of one of the master nodes solr4 [image: Screen Shot 2019-09-03 at 3.37.08 PM.png]
solr8 [image: Screen Shot 2019-09-03 at 3.45.46 PM.png] *Manzama*a MODERN GOVERNANCE company Russell Bahr Lead Infrastructure Engineer USA & CAN Office: +1 (541) 306 3271 USA & CAN Support: +1 (541) 706 9393 UK Office & Support: +44 (0)203 282 1633 AUS Office & Support: +61 (0) 2 8417 2339 543 NW York Drive, Suite 100, Bend, OR 97703 LinkedIn <http://www.linkedin.com/company/manzama> | Twitter <https://twitter.com/ManzamaInc> | Facebook <http://www.facebook.com/manzamainc> | YouTube <https://www.youtube.com/channel/UCBo3QoqewyNoo7HiT_BFuRw> On Tue, Sep 3, 2019 at 2:19 PM Shawn Heisey <apa...@elyograg.org> wrote: > On 9/3/2019 1:22 PM, Russell Bahr wrote: > > Yes, some of our queries are quite complex due to a lot of very specific > > positive as well as negative boosts, however, the query that I ran as the > > base test after we found our queries were taking so long is just " > > > http://solr.obscured.com:8990/solr/content/select?q=*%3A*&wt=json&indent=true > > " > > If you've got an all documents query (the special *:* syntax) taking > many seconds to run, that is usually an indication of a serious > performance problem. In most situations, I would expect the millisecond > response time to be only two or three digits, especially with your > relatively low document count. > > The response times are worse with the new version, but I would call the > response times on the old version very slow as well. > > The screenshot described here is someplace we can start looking for > performance issues: > > > https://cwiki.apache.org/confluence/display/solr/SolrPerformanceProblems#SolrPerformanceProblems-ProcesslistingonPOSIXoperatingsystems > > Thanks, > Shawn >
