andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,476 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
1103379e02
Go to file
Norman Maurer 1103379e02 Allow to disable reference count checks on every access of the ByteBuf 
Motiviation:

Checking reference count on every access on a ByteBuf can have some big performance overhead depending on how the access pattern is. If the user is sure that there are no reference count errors on his side it should be possible to disable the check and so gain the max performance.

Modification:

- Add io.netty.buffer.bytebuf.checkAccessible system property which allows to disable the checks. Enabled by default.
- Add microbenchmark

Result:

Increased performance for operations on the ByteBuf.
2015-10-15 10:19:49 +02:00
all [maven-release-plugin] prepare for next development iteration 2015-09-30 09:31:26 +02:00
buffer Allow to disable reference count checks on every access of the ByteBuf 2015-10-15 10:19:49 +02:00
codec [#4284] Forward decoded messages more frequently 2015-10-07 14:15:14 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2015-09-30 09:31:26 +02:00
codec-http [#4327] Ensure toString() will not throw IllegalReferenceCountException 2015-10-10 20:12:19 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-09-30 09:31:26 +02:00
common [#4284] Forward decoded messages more frequently 2015-10-07 14:15:14 +02:00
example [#4347] Remove not needed write operation from example. 2015-10-14 10:56:49 +02:00
handler Reduce object creation for for unwrap/wrap if no ByteBuffer[] is used. 2015-10-07 13:35:44 +02:00
license Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
microbench Allow to disable reference count checks on every access of the ByteBuf 2015-10-15 10:19:49 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2015-09-30 09:31:26 +02:00
testsuite [maven-release-plugin] prepare for next development iteration 2015-09-30 09:31:26 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2015-09-30 09:31:26 +02:00
transport change type definition of pipeline from DefaultChannelPipeline to ChannelPipeline 2015-10-10 20:16:07 +02:00
transport-native-epoll EPOLL RDHUP and IN at same time 2015-10-06 14:21:35 -07:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2015-09-30 09:31:26 +02:00
transport-sctp [#4327] Ensure toString() will not throw IllegalReferenceCountException 2015-10-10 20:12:19 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2015-09-30 09:31:26 +02:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Add JVM crash logs to .gitignore 2014-05-18 21:37:12 +09:00
.travis.yml Travis CI branch whitelisting 2013-03-11 09:55:43 +09:00
CONTRIBUTING.md Move the pull request guide to the developer guide 2014-03-12 13:18:14 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
pom.xml Add support for server-side renegotiation when using OpenSslEngine. 2015-10-02 11:24:31 +02:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:43 -07:00
run-example.sh Add logLevel property to enable different log levels for the examples. 2014-11-21 10:48:13 +09:00

README.md

Netty Project

Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.

Links

How to build

For the detailed information about building and developing Netty, please visit the developer guide. This page only gives very basic information.

You require the following to build Netty:

Note that this is build-time requirement. JDK 5 (for 3.x) or 6 (for 4.0+) is enough to run your Netty-based application.

Branches to look

The 'master' branch is where the development of the latest major version lives on. The development of all other major versions takes place in each branch whose name is identical to its major version number. For example, the development of 3.x and 4.x resides in the branch '3' and the branch '4' respectively.