You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Fuad Efendi <fu...@efendi.ca> on 2011/07/27 21:56:06 UTC

Solr Performance Tuning: -XX:+AggressiveOpts

Anyone tried this? I can not start Solr-Tomcat with following options on
Ubuntu:

JAVA_OPTS="$JAVA_OPTS -Xms2048m -Xmx2048m -Xmn256m -XX:MaxPermSize=256m"
JAVA_OPTS="$JAVA_OPTS -Dsolr.solr.home=/data/solr -Dfile.encoding=UTF8
-Duser.timezone=GMT
-Djava.util.logging.config.file=/data/solr/logging.properties
-Djava.net.preferIPv4Stack=true"
JAVA_OPTS="$JAVA_OPTS -XX:+UseParNewGC -XX:+UseConcMarkSweepGC
-XX:+CMSIncrementalMode  -XX:+AggressiveOpts -XX:NewSize=64m
-XX:MaxNewSize=64m -XX:CMSInitiatingOccupancyFraction=77
-XX:+CMSParallelRemarkEnabled"
JAVA_OPTS="$JAVA_OPTS -verbose:gc  -XX:+PrintGCDetails
-XX:+PrintGCDateStamps -Xloggc:/data/solr/solr-gc.log"


Tomcat log (something about PorterStemFilter; Solr 3.3.0):

INFO: Server startup in 2683 ms
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f5c6f36716e, pid=7713, tid=140034519381760
#
# JRE version: 6.0_26-b03
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.1-b02 mixed mode
linux-amd64 compressed oops)
# Problematic frame:
# J  org.apache.lucene.analysis.PorterStemFilter.incrementToken()Z
#
[thread 140034523637504 also had an error]
[thread 140034520434432 also had an error]
# An error report file with more information is saved as:
# [thread 140034520434432 also had an error]
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#



However, I can start it and run without any problems by removing
-XX:+AggressiveOpts (which has to be default setting "in upcoming releases"
Java 6)



Do we need to disable -XX:-DoEscapeAnalysis as IBM suggests?
http://www-01.ibm.com/support/docview.wss?uid=swg21422605



Thanks,
Fuad Efendi

http://www.tokenizer.ca



Re: Solr Performance Tuning: -XX:+AggressiveOpts

Posted by Doug Meil <do...@explorysmedical.com>.
Thanks, I'll make sure the book has a ref to this.





On 7/27/11 9:00 PM, "Andrew Purtell" <ap...@apache.org> wrote:

>This is the conversation:
>http://lucene.472066.n3.nabble.com/Solr-Performance-Tuning-XX-AggressiveOp
>ts-td3204659.html
>
>
>----- Forwarded Message -----
>>From: Robert Muir <rc...@gmail.com>
>>To: solr-user@lucene.apache.org
>>Sent: Wednesday, July 27, 2011 1:19 PM
>>Subject: Re: Solr Performance Tuning: -XX:+AggressiveOpts
>>
>>On Wed, Jul 27, 2011 at 4:12 PM, Fuad Efendi <fu...@efendi.ca> wrote:
>>> Thanks Robert!!!
>>>
>>> "Submitted On 26-JUL-2011" - yesterday.
>>>
>>> This option was popular in HbaseŠ
>>
>>Then you should tell them also, not to use it, if they want their loops
>>to work.
>>
>>-- 
>>lucidimagination.com
>>
>>


Fw: Solr Performance Tuning: -XX:+AggressiveOpts

Posted by Andrew Purtell <ap...@apache.org>.
This is the conversation: http://lucene.472066.n3.nabble.com/Solr-Performance-Tuning-XX-AggressiveOpts-td3204659.html


----- Forwarded Message -----
>From: Robert Muir <rc...@gmail.com>
>To: solr-user@lucene.apache.org
>Sent: Wednesday, July 27, 2011 1:19 PM
>Subject: Re: Solr Performance Tuning: -XX:+AggressiveOpts
>
>On Wed, Jul 27, 2011 at 4:12 PM, Fuad Efendi <fu...@efendi.ca> wrote:
>> Thanks Robert!!!
>>
>> "Submitted On 26-JUL-2011" - yesterday.
>>
>> This option was popular in HbaseŠ
>
>Then you should tell them also, not to use it, if they want their loops to work.
>
>-- 
>lucidimagination.com
>
>
>

Re: Solr Performance Tuning: -XX:+AggressiveOpts

Posted by Robert Muir <rc...@gmail.com>.
On Wed, Jul 27, 2011 at 4:12 PM, Fuad Efendi <fu...@efendi.ca> wrote:
> Thanks Robert!!!
>
> "Submitted On 26-JUL-2011" - yesterday.
>
> This option was popular in HbaseŠ

Then you should tell them also, not to use it, if they want their loops to work.

-- 
lucidimagination.com

Re: Solr Performance Tuning: -XX:+AggressiveOpts

Posted by Fuad Efendi <fu...@efendi.ca>.
Thanks Robert!!!

"Submitted On 26-JUL-2011" - yesterday.

This option was popular in HbaseŠ


On 11-07-27 3:58 PM, "Robert Muir" <rc...@gmail.com> wrote:

>Don't use this option, these optimizations are buggy:
>
>http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7070134
>
>
>On Wed, Jul 27, 2011 at 3:56 PM, Fuad Efendi <fu...@efendi.ca> wrote:
>> Anyone tried this? I can not start Solr-Tomcat with following options on
>> Ubuntu:
>>
>> JAVA_OPTS="$JAVA_OPTS -Xms2048m -Xmx2048m -Xmn256m -XX:MaxPermSize=256m"
>> JAVA_OPTS="$JAVA_OPTS -Dsolr.solr.home=/data/solr -Dfile.encoding=UTF8
>> -Duser.timezone=GMT
>> -Djava.util.logging.config.file=/data/solr/logging.properties
>> -Djava.net.preferIPv4Stack=true"
>> JAVA_OPTS="$JAVA_OPTS -XX:+UseParNewGC -XX:+UseConcMarkSweepGC
>> -XX:+CMSIncrementalMode  -XX:+AggressiveOpts -XX:NewSize=64m
>> -XX:MaxNewSize=64m -XX:CMSInitiatingOccupancyFraction=77
>> -XX:+CMSParallelRemarkEnabled"
>> JAVA_OPTS="$JAVA_OPTS -verbose:gc  -XX:+PrintGCDetails
>> -XX:+PrintGCDateStamps -Xloggc:/data/solr/solr-gc.log"
>>
>>
>> Tomcat log (something about PorterStemFilter; Solr 3.3.0):
>>
>> INFO: Server startup in 2683 ms
>> #
>> # A fatal error has been detected by the Java Runtime Environment:
>> #
>> #  SIGSEGV (0xb) at pc=0x00007f5c6f36716e, pid=7713, tid=140034519381760
>> #
>> # JRE version: 6.0_26-b03
>> # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.1-b02 mixed mode
>> linux-amd64 compressed oops)
>> # Problematic frame:
>> # J  org.apache.lucene.analysis.PorterStemFilter.incrementToken()Z
>> #
>> [thread 140034523637504 also had an error]
>> [thread 140034520434432 also had an error]
>> # An error report file with more information is saved as:
>> # [thread 140034520434432 also had an error]
>> #
>> # If you would like to submit a bug report, please visit:
>> #   http://java.sun.com/webapps/bugreport/crash.jsp
>> #
>>
>>
>>
>> However, I can start it and run without any problems by removing
>> -XX:+AggressiveOpts (which has to be default setting "in upcoming
>>releases"
>> Java 6)
>>
>>
>>
>> Do we need to disable -XX:-DoEscapeAnalysis as IBM suggests?
>> http://www-01.ibm.com/support/docview.wss?uid=swg21422605
>>
>>
>>
>> Thanks,
>> Fuad Efendi
>>
>> http://www.tokenizer.ca
>>
>>
>>
>
>
>
>-- 
>lucidimagination.com



Re: Solr Performance Tuning: -XX:+AggressiveOpts

Posted by Robert Muir <rc...@gmail.com>.
Don't use this option, these optimizations are buggy:

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7070134


On Wed, Jul 27, 2011 at 3:56 PM, Fuad Efendi <fu...@efendi.ca> wrote:
> Anyone tried this? I can not start Solr-Tomcat with following options on
> Ubuntu:
>
> JAVA_OPTS="$JAVA_OPTS -Xms2048m -Xmx2048m -Xmn256m -XX:MaxPermSize=256m"
> JAVA_OPTS="$JAVA_OPTS -Dsolr.solr.home=/data/solr -Dfile.encoding=UTF8
> -Duser.timezone=GMT
> -Djava.util.logging.config.file=/data/solr/logging.properties
> -Djava.net.preferIPv4Stack=true"
> JAVA_OPTS="$JAVA_OPTS -XX:+UseParNewGC -XX:+UseConcMarkSweepGC
> -XX:+CMSIncrementalMode  -XX:+AggressiveOpts -XX:NewSize=64m
> -XX:MaxNewSize=64m -XX:CMSInitiatingOccupancyFraction=77
> -XX:+CMSParallelRemarkEnabled"
> JAVA_OPTS="$JAVA_OPTS -verbose:gc  -XX:+PrintGCDetails
> -XX:+PrintGCDateStamps -Xloggc:/data/solr/solr-gc.log"
>
>
> Tomcat log (something about PorterStemFilter; Solr 3.3.0):
>
> INFO: Server startup in 2683 ms
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x00007f5c6f36716e, pid=7713, tid=140034519381760
> #
> # JRE version: 6.0_26-b03
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.1-b02 mixed mode
> linux-amd64 compressed oops)
> # Problematic frame:
> # J  org.apache.lucene.analysis.PorterStemFilter.incrementToken()Z
> #
> [thread 140034523637504 also had an error]
> [thread 140034520434432 also had an error]
> # An error report file with more information is saved as:
> # [thread 140034520434432 also had an error]
> #
> # If you would like to submit a bug report, please visit:
> #   http://java.sun.com/webapps/bugreport/crash.jsp
> #
>
>
>
> However, I can start it and run without any problems by removing
> -XX:+AggressiveOpts (which has to be default setting "in upcoming releases"
> Java 6)
>
>
>
> Do we need to disable -XX:-DoEscapeAnalysis as IBM suggests?
> http://www-01.ibm.com/support/docview.wss?uid=swg21422605
>
>
>
> Thanks,
> Fuad Efendi
>
> http://www.tokenizer.ca
>
>
>



-- 
lucidimagination.com