activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From clebertsuconic <>
Subject [GitHub] activemq-6 pull request: ACTIVEMQ6-78 performance improvements
Date Wed, 11 Feb 2015 17:43:59 GMT
GitHub user clebertsuconic opened a pull request:

    ACTIVEMQ6-78 performance improvements


You can merge this pull request into a Git repository by running:

    $ git pull perf

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #95
commit 8b0063fd573f0b45c1da222ab9e538f65b3c66e7
Author: Clebert Suconic <>
Date:   2015-02-10T15:53:02Z

    ACTIVEMQ6-78 Adding tests to evaluate this task
    This commit is just adding tests I used to debug the blocked calls issue
    There are some profiling parameters you can use that I added as a comment to the pom
    The reason this is a separate commit is that it could be easier to validate the results
of optimizations
    checking after and before any changes

commit 0a6edee8b58d3db9c3c063ab7c9b1bcd53ba427b
Author: Clebert Suconic <>
Date:   2015-02-10T16:30:18Z

    ACTIVEMQ6-78 Improving performance over Netty NIO blocked calls performance work
    There are two aspects of this work. First avoid asynchronous packets and avoid
    context switch over the executors. Packet had a method to make certain packets such
    as commit to use a different executor. Since it's NIO everything is done at the Netty
thread now.
    The second aspect was to make sure we use the proper buffering

commit 88f13f267f7a88b529fb7bfa7b6578dc62ef863c
Author: Clebert Suconic <>
Date:   2015-02-11T13:36:17Z

    Fixing test failure
    This test started to fail after performance improvements from  ACTIVEMQ6-78
    After some investigation it turned out that this test was racing with the client
    crashing even before the queue was created or sending a non persistent message
    asynchronously while the client crashed before the server received the message.
    I've also decreased some of the times on pings so the test could run a bit faster


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 or file a JIRA ticket
with INFRA.

View raw message