You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "bidorbuy (JIRA)" <ji...@apache.org> on 2017/11/03 08:39:00 UTC
[jira] [Comment Edited] (SOLR-11078) Solr query performance
degradation since Solr 6.4.2
[ https://issues.apache.org/jira/browse/SOLR-11078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237277#comment-16237277 ]
bidorbuy edited comment on SOLR-11078 at 11/3/17 8:38 AM:
----------------------------------------------------------
Thank you [~jpountz] for the explanation. We have now been running Solr 7.1.0 and Solr 6.4.0 loadbalanced for about an hour of production load and I can confirm that response time on 7.1.0 using TrieFields (i.e. the same schema we use on Solr 6.4.0) is about 10-20% faster on Solr 7.1.0.
Also interesting to note is that on Solr 6.4.0 the load-average sites at 2.26 (4 cores) and Cpu is at 50-73%. On Solr 7.1.0 load-average is at 1.4 and CPU is around 20-30%.
You can see this in the graph below (zasolrm03 = Solr 7.1.0 / zasolrm02 = Solr 6.4.0) - weswitched zasolrm03/7.1.0 into the load-balancer at 09:44 - hence the initial warmup spike:
!solr-71-vs-64.png!
was (Author: tech@bidorbuy.co.za):
Thank you [~jpountz] for the explanation. We have now been running Solr 7.1.0 and Solr 6.4.0 loadbalanced for about an hour of production load and I can confirm that response time on 7.1.0 using TrieFields (i.e. the same schema we use on Solr 6.4.0) is about 10-20% faster on Solr 7.1.0.
Also interesting to note is that on Solr 6.4.0 the load-average sites at 2.26 (4 cores) and Cpu is at 50-73%. On Solr 7.1.0 load-average is at 1.4 and CPU is around 20-30%.
You can see this in the graph below (zasolrm03 = Solr 7.1.0 / zasolrm02 = Solr 6.4.0):
!solr-71-vs-64.png!
> Solr query performance degradation since Solr 6.4.2
> ---------------------------------------------------
>
> Key: SOLR-11078
> URL: https://issues.apache.org/jira/browse/SOLR-11078
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: search, Server
> Affects Versions: 6.6, 7.1
> Environment: * CentOS 7.3 (Linux zasolrm03 3.10.0-514.26.2.el7.x86_64 #1 SMP Tue Jul 4 15:04:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux)
> * Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
> * 4 CPU, 10GB RAM
> Running Solr 6.6.0 with the following JVM settings:
> java -server -Xms4G -Xmx4G -XX:NewRatio=3 -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=90 -XX:MaxTenuringThreshold=8 -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:ConcGCThreads=4 -XX:ParallelGCThreads=4 -XX:+CMSScavengeBeforeRemark -XX:PretenureSizeThreshold=64m -XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=50 -XX:CMSMaxAbortablePrecleanTime=6000 -XX:+CMSParallelRemarkEnabled -XX:+ParallelRefProcEnabled -verbose:gc -XX:+PrintHeapAtGC -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+PrintTenuringDistribution -XX:+PrintGCApplicationStoppedTime -Xloggc:/home/prodza/solrserver/../logs/solr_gc.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=9 -XX:GCLogFileSize=20M -Dsolr.log.dir=/home/prodza/solrserver/../logs -Djetty.port=8983 -DSTOP.PORT=7983 -DSTOP.KEY=solrrocks -Duser.timezone=SAST -Djetty.home=/home/prodza/solrserver/server -Dsolr.solr.home=/home/prodza/solrserver/../solr -Dsolr.install.dir=/home/prodza/solrserver -Dlog4j.configuration=file:/home/prodza/solrserver/../config/log4j.properties -Xss256k -Xss256k -Dsolr.log.muteconsole -XX:OnOutOfMemoryError=/home/prodza/solrserver/bin/oom_solr.sh 8983 /home/prodza/solrserver/../logs -jar start.jar --module=http
> Reporter: bidorbuy
> Priority: Major
> Attachments: compare-6.4.2-6.6.0.png, core-admin-tradesearch.png, jvm-stats.png, schema.xml, screenshot-1.png, screenshot-2.png, solr-6-4-2-schema.xml, solr-6-4-2-solrconfig.xml, solr-7-1-0-managed-schema, solr-7-1-0-solrconfig.xml, solr-71-vs-64.png, solr-sample-warning-log.txt, solr.in.sh, solrconfig.xml
>
>
> We are currently running 2 separate Solr servers - refer to screenshots:
> * zasolrm02 is running on Solr 6.4.2
> * zasolrm03 is running on Solr 6.6.0
> Both servers have the same OS / JVM configuration and are using their own indexes. We round-robin load-balance through our Tomcats and notice that Since Solr 6.4.2 performance has dropped. We have two indices per server "searchsuggestions" and "tradesearch". There is a noticeable drop in performance since Solr 6.4.2.
> I am not sure if this is perhaps related to metric collation or other underlying changes. I am not sure if other high transaction users have noticed similar issues.
> *1) zasolrm03 (6.6.0) is almost twice as slow on the tradesearch index:*
> !compare-6.4.2-6.6.0.png!
> *2) This is also visible in the searchsuggestion index:*
> !screenshot-1.png!
> *3) The Tradesearch index shows the biggest difference:*
> !screenshot-2.png!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org