You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by schalmers <si...@manufacturingintelligence.com.au> on 2018/11/26 07:32:48 UTC
Artemis max performance capped at ~200MB/s
Is there any reason why running some Artemis performance tests I cannot get
more than ~200MB/s (1.6 gbits/s) through an Artemis v2.6.3 broker running on
a Amazon Linux VM with 16 vCPU, 32GB RAM?
artemis.profile:
broker.xml:
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: Artemis max performance capped at ~200MB/s
Posted by schalmers <si...@manufacturingintelligence.com.au>.
jbertram wrote
> Do you have any metrics on the network utilization between
> the live and the backup?
In terms of the network utilization between the live and the backup, using
iperf3 I get these results:
[ec2-user@ip-172-31-30-42 ~]$ iperf3 -c 172.31.10.32 -p 5672
Connecting to host 172.31.10.32, port 5672
[ 4] local 172.31.30.42 port 51508 connected to 172.31.10.32 port 5672
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 589 MBytes 4.94 Gbits/sec 0 1.16 MBytes
[ 4] 1.00-2.00 sec 592 MBytes 4.97 Gbits/sec 0 1.23 MBytes
[ 4] 2.00-3.00 sec 592 MBytes 4.97 Gbits/sec 0 1.23 MBytes
[ 4] 3.00-4.00 sec 594 MBytes 4.98 Gbits/sec 0 1.23 MBytes
[ 4] 4.00-5.00 sec 592 MBytes 4.97 Gbits/sec 0 1.23 MBytes
[ 4] 5.00-6.00 sec 592 MBytes 4.97 Gbits/sec 0 1.41 MBytes
[ 4] 6.00-7.00 sec 594 MBytes 4.98 Gbits/sec 0 1.41 MBytes
[ 4] 7.00-8.00 sec 592 MBytes 4.97 Gbits/sec 0 1.41 MBytes
[ 4] 8.00-9.00 sec 592 MBytes 4.97 Gbits/sec 0 1.41 MBytes
[ 4] 9.00-10.00 sec 594 MBytes 4.98 Gbits/sec 0 1.41 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.00 sec 5.79 GBytes 4.97 Gbits/sec 0 sender
[ 4] 0.00-10.00 sec 5.78 GBytes 4.97 Gbits/sec
receiver
jbertram wrote
> What happens if you run with both the live and
> the backup on the same machine (obviously not something you'd do in
> production, but something worth testing as a troubleshooting exercise
> IMO).
Doing so, I get ~400MB/s (~3.2gbit/s) which is expected, as it is hitting
the storage network limit of 3.5gbit/s as provided by AWS.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: Artemis max performance capped at ~200MB/s
Posted by Justin Bertram <jb...@apache.org>.
None of the XML you pasted is visible in the email (although it is visible
if I use the Nabble link).
In general there will be a performance hit from replication. That's one of
the trade-offs between replication and shared-storage. Using
shared-storage the data only has to be written once, but with replication
the data has to be written on the live and then sent across the network
again and written on the backup as well. Whether or not you're seeing the
expected performance hit is the real question, and I'm not sure how to
answer that. Do you have any metrics on the network utilization between
the live and the backup? What happens if you run with both the live and
the backup on the same machine (obviously not something you'd do in
production, but something worth testing as a troubleshooting exercise IMO).
Justin
On Mon, Nov 26, 2018 at 1:33 AM schalmers <
simon.chalmers@manufacturingintelligence.com.au> wrote:
> Is there any reason why running some Artemis performance tests I cannot get
> more than ~200MB/s (1.6 gbits/s) through an Artemis v2.6.3 broker running
> on
> a Amazon Linux VM with 16 vCPU, 32GB RAM?
>
> artemis.profile:
>
>
>
> broker.xml:
>
>
>
>
>
> --
> Sent from:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
>