From users-return-50722-archive-asf-public=cust-asf.ponee.io@activemq.apache.org Mon Nov 26 21:04:35 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 45E9F180647 for ; Mon, 26 Nov 2018 21:04:35 +0100 (CET) Received: (qmail 38318 invoked by uid 500); 26 Nov 2018 20:04:34 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 38307 invoked by uid 99); 26 Nov 2018 20:04:34 -0000 Received: from mail-relay.apache.org (HELO mailrelay1-lw-us.apache.org) (207.244.88.152) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Nov 2018 20:04:34 +0000 Received: from mail-oi1-f178.google.com (mail-oi1-f178.google.com [209.85.167.178]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 08E713BB4 for ; Mon, 26 Nov 2018 20:04:32 +0000 (UTC) Received: by mail-oi1-f178.google.com with SMTP id x23so17090123oix.3 for ; Mon, 26 Nov 2018 12:04:32 -0800 (PST) X-Gm-Message-State: AGRZ1gJXCqTTHT+clXYQ9SBfdlI6YlHSY4R7X8acfE7ReXq2aBobHtmK f9KrGNsTKRF/GDCVz+1rNtOfir7FrhkcPi40EgrkAQ== X-Google-Smtp-Source: AJdET5dglT0J5s0DrjsE0vntOPAjyUCD3f76Bv0ESvPtteA6CyGDQgwUC3OBFM1NOQymdg+CMlY04CkDIOsG9kXE3d0= X-Received: by 2002:aca:5d83:: with SMTP id r125-v6mr17029125oib.227.1543262672428; Mon, 26 Nov 2018 12:04:32 -0800 (PST) MIME-Version: 1.0 References: <1543217568653-0.post@n4.nabble.com> In-Reply-To: <1543217568653-0.post@n4.nabble.com> From: Justin Bertram Date: Mon, 26 Nov 2018 14:04:21 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Artemis max performance capped at ~200MB/s To: users@activemq.apache.org Content-Type: multipart/alternative; boundary="0000000000006311ed057b96d7dc" --0000000000006311ed057b96d7dc Content-Type: text/plain; charset="UTF-8" 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 > --0000000000006311ed057b96d7dc--