activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From franz1981 <...@git.apache.org>
Subject [GitHub] activemq-artemis issue #1268: ARTEMIS-1162: Make new TimedBuffer Configurabl...
Date Mon, 15 May 2017 09:22:44 GMT
Github user franz1981 commented on the issue:

    https://github.com/apache/activemq-artemis/pull/1268
  
    @michaelandrepearce 
    
    > 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
    :100: 
    > some changes may start to even step on each other, e.g. one fix may actually regress
another
    Having a default load generator with different test cases against agreed metrics to make
easier identify evident performance changes is a nice idea indeed!
    IMHO the hardest part (for me! I'm giving space to devs more math skilled than me) is
to identify the responsibility of a single point of change in a end 2 end result.
    
    I suspect that having proper performance counters on the broker to be collected by user/devs
using their own tests (ie with their SLAs in mind) are an additional tool that could help
to identify isolated code changes perf changes. 
    I smell this could be a good forum discussion to start some thought around this :)


---
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.
---

Mime
View raw message