activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jose MarĂ­a Zaragoza <demablo...@gmail.com>
Subject Re: Java Options
Date Wed, 22 Jan 2014 20:02:11 GMT
2014/1/22 Rodrigo Ramos <crackduoro@gmail.com>:
> 5.8.0
>
>
> 2014/1/22 Claus Ibsen <claus.ibsen@gmail.com>
>
>> What version of ActiveMQ are you using?
>>
>> On Wed, Jan 22, 2014 at 7:37 PM, Rodrigo Ramos <crackduoro@gmail.com>
>> wrote:
>> > Hello Everybody
>> >
>> > I want to change how to GC perform into in activemq. I have edited the
>> > starting shell and I have seen some memory variables.
>> >
>> > If I edit the starting shell with follow parameters:
>> >
>> > export ACTIVEMQ_HOME=/opt/apache-activemq-5.8.0
>> > export ACTIVEMQ_BASE=$ACTIVEMQ_BASE
>> > export ACTIVEMQ_OPTS_MEMORY="-Xms2G -Xmx2G"
>> >
>> > *${ACTIVEMQ_HOME}/bin/activemq -XX:-UseParallelGC "$*"*
>> >
>> >
>> > I get the follow error:
>> >
>> > INFO: Unrecognized option: -XX:-UseParallelGC
>> >


Are you try

-XX:UseParallelGC

?


The parallel copying collector (Enabled using -XX:+UseParNewGC). Like
the original copying collector, this is a stop-the-world collector.
However this collector parallelizes the copying collection over
multiple threads, which is more efficient than the original
single-thread copying collector for multi-CPU machines (though not for
single-CPU machines). This algorithm potentially speeds up young
generation collection by a factor equal to the number of CPUs
available, when compared to the original singly-threaded copying
collector.

The parallel scavenge collector (Enabled using -XX:UseParallelGC).
This is like the previous parallel copying collector, but the
algorithm is tuned for gigabyte heaps (over 10GB) on multi-CPU
machines. This collection algorithm is designed to maximize throughput
while minimizing pauses. It has an optional adaptive tuning policy
which will automatically resize heap spaces. If you use this
collector, you can only use the the original mark-sweep collector in
the old generation (i.e. the newer old generation concurrent collector
cannot work with this young generation collector).









>> >
>> > How can I set this parameters?
>> >
>> >
>> > Thanks for your help.
>> >
>> > Regards
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> Email: cibsen@redhat.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>> Make your Camel applications look hawt, try: http://hawt.io
>>

Mime
View raw message