Go to file
Francesco Nigro 1cf2687244 Fixed JMH ByteBuf benchmark to avoid dead code elimination
Motivation:

The JMH doc suggests to use BlackHoles to avoid dead code elimination hence would be better to follow this best practice.

Modifications:

Each benchmark method is returning the ByteBuf/ByteBuffer to avoid the JVM to perform any dead code elimination.

Result:

The results are more reliable and comparable to the others provided by other ByteBuf benchmarks (eg HeapByteBufBenchmark)
2017-12-19 14:09:18 +01:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:26 -08:00
all [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
bom [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
buffer [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
codec [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
codec-dns [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
codec-http [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
codec-http2 codec-http2: Better keep track of nameLength in HpackDecoder.decode 2017-12-18 17:41:09 -08:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
codec-redis [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
codec-socks [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
codec-xml [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
common Remove WeakOrderedQueue from WeakHashMap when FastThreadLocal value was removed if possible. 2017-12-15 21:21:18 +01:00
dev-tools [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
example [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
handler [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
license Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
microbench Fixed JMH ByteBuf benchmark to avoid dead code elimination 2017-12-19 14:09:18 +01:00
resolver [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
tarball [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
testsuite [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
testsuite-http2 Add h2spec test suite module to check if netty http2 implementation conforms with the specification 2017-12-16 13:18:19 +01:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
transport added overloaded method to the DefaultChannelPipeline in order to avoid unnecessary allocation 2017-12-18 09:34:05 +01:00
transport-native-epoll [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
transport-native-kqueue [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
transport-native-unix-common [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
transport-native-unix-common-tests [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
transport-udt [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:19:45 +02: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:13:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
pom.xml Add h2spec test suite module to check if netty http2 implementation conforms with the specification 2017-12-16 13:18:19 +01:00
README.md Adding stable JDK9 module names that follow reverse-DNS style 2017-11-29 11:50:24 +01:00
run-example.sh Add UptimeServer and adjust UptimeClient's code style. 2017-04-28 07:41:07 +02:00

Netty Project

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

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

Development of all versions takes place in each branch whose name is identical to <majorVersion>.<minorVersion>. For example, the development of 3.9 and 4.0 resides in the branch '3.9' and the branch '4.0' respectively.

Usage with JDK 9

Netty can be used in modular JDK9 applications as a collection of automatic modules. The module names follow the reverse-DNS style, and are derived from subproject names rather than root packages due to historical reasons. They are listed below:

  • io.netty.buffer
  • io.netty.codec
  • io.netty.codec.dns
  • io.netty.codec.haproxy
  • io.netty.codec.http
  • io.netty.codec.http2
  • io.netty.codec.memcache
  • io.netty.codec.mqtt
  • io.netty.codec.redis
  • io.netty.codec.smtp
  • io.netty.codec.socks
  • io.netty.codec.stomp
  • io.netty.codec.xml
  • io.netty.common
  • io.netty.handler
  • io.netty.handler.proxy
  • io.netty.resolver
  • io.netty.resolver.dns
  • io.netty.transport
  • io.netty.transport.epoll (native omitted - reserved keyword in Java)
  • io.netty.transport.kqueue (native omitted - reserved keyword in Java)
  • io.netty.transport.unix.common (native omitted - reserved keyword in Java)
  • io.netty.transport.rxtx
  • io.netty.transport.sctp
  • io.netty.transport.udt

Automatic modules do not provide any means to declare dependencies, so you need to list each used module separately in your module-info file.