[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cassandra-dev
Subject:    [GitHub] cassandra pull request: Various improvements in netty usage
From:       normanmaurer <git () git ! apache ! org>
Date:       2014-05-08 18:42:14
Message-ID: git-pr-35-cassandra () git ! apache ! org
[Download RAW message or body]

GitHub user normanmaurer opened a pull request:

    https://github.com/apache/cassandra/pull/35

    Various improvements in netty usage

    

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

    $ git pull https://github.com/normanmaurer/cassandra netty_4

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

    https://github.com/apache/cassandra/pull/35.patch

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

    This closes #35
    
----
commit da6c6c4cb9265b3a486f2346a50a1240467c9d89
Author: Norman Maurer <nmaurer@redhat.com>
Date:   2014-05-08T18:07:44Z

    Various fixes to improve performance. This includes:
     * use the same ByteBufAllocator everywhere
     * use ByteBuf.slice(...) when possible to reduce memory copies
     * Correctly handle the writerIndex with arrayOffset()

commit 1747db172d65e4c84950dafd270546b4ae0bafd3
Author: Norman Maurer <nmaurer@redhat.com>
Date:   2014-05-08T18:09:45Z

    Bump up netty version to 4.0.19.Final for performance improvements
    
    This is mainly because of the new introduced ThreadLocal caches for the \
PooledByteBufAllocator (was introduced in 4.0.18.Final).

----


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


[prev in list] [next in list] [prev in thread] [next in thread]