Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
From: michaelandrepearce <git@git.apache.org>
To: dev@activemq.apache.org
Reply-To: dev@activemq.apache.org
References: <git-pr-1268-activemq-artemis@git.apache.org>
In-Reply-To: <git-pr-1268-activemq-artemis@git.apache.org>
Subject: [GitHub] activemq-artemis issue #1268: ARTEMIS-1162: Make new TimedBuffer Configurabl...
Content-Type: text/plain
Message-Id: <20170515082725.F2AE0DFFB3@git1-us-west.apache.org>
Date: Mon, 15 May 2017 08:27:25 +0000 (UTC)
archived-at: Mon, 15 May 2017 08:27:28 -0000

Github user michaelandrepearce commented on the issue:

    https://github.com/apache/activemq-artemis/pull/1268
  
    @franz1981 and here in lies the issue, that the project doesn't currently have a set of agreed performance metrics for different end 2 end scenarios, that are run automatically and reported each release. 
    
    I like micro benchmarks as they help isolate a problem, and quickly test if the changes look promising and the best we have today.
    
    As we move to look at other perf improvements without the end 2 end scenarios reporting perf metrics version to version, some changes may start to even step on each other, e.g. one fix may actually regress another, e.g. the classical, batching can improve throughput very easily but trades it for latency.
    
    
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---