andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
5,803 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
4ad3984c8b
Go to file
Norman Maurer 4ad3984c8b [#2436] Unsafe*ByteBuf implementation should only invert bytes if ByteOrder differ from native ByteOrder 
Motivation:
Our Unsafe*ByteBuf implementation always invert bytes when the native ByteOrder is LITTLE_ENDIAN (this is true on intel), even when the user calls order(ByteOrder.LITTLE_ENDIAN). This is not optimal for performance reasons as the user should be able to set the ByteOrder to LITTLE_ENDIAN and so write bytes without the extra inverting.

Modification:
- Introduce a new special SwappedByteBuf (called UnsafeDirectSwappedByteBuf) that is used by all the Unsafe*ByteBuf implementation and allows to write without inverting the bytes.
- Add benchmark
- Upgrade jmh to 0.8

Result:
The user is be able to get the max performance even on servers that have ByteOrder.LITTLE_ENDIAN as their native ByteOrder.
2014-06-05 11:09:58 +02:00
all Use a forked exec-maven-plugin instead of maven-antrun-plugin 2014-05-23 20:06:12 +09:00
buffer [#2436] Unsafe*ByteBuf implementation should only invert bytes if ByteOrder differ from native ByteOrder 2014-06-05 11:09:58 +02:00
codec [#2525] Use VoidChannelPromise in MessageToMessageEncoder when possible 2014-06-01 19:26:09 +02:00
codec-http codec-http: Document the semantics of HttpResponseStatus equality and comparison 2014-05-30 07:52:42 +02:00
codec-socks Clean up the examples 2014-05-23 17:19:34 +09:00
common Clean up MpscLinkedQueue, fix its leak, and make it work without Unsafe 2014-06-04 03:24:05 +09:00
example OkResponseHandler should return a FullHttpResponse. 2014-06-03 09:44:04 +02:00
handler [#2494] Fix data curruption by ChannelTrafficShapingHandler 2014-06-03 08:38:23 +02:00
license Preparation for porting OpenSSL support in 3.10 2014-05-17 20:01:47 +09:00
microbench [#2436] Unsafe*ByteBuf implementation should only invert bytes if ByteOrder differ from native ByteOrder 2014-06-05 11:09:58 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2014-04-30 15:40:54 +02:00
testsuite Add an OpenSslEngine and the universal API for enabling SSL 2014-05-18 02:54:23 +09:00
transport ChannelFlushPromiseNotifier should allow long value for pendingDataSize 2014-06-03 17:34:04 +02:00
transport-native-epoll Add an OpenSslEngine and the universal API for enabling SSL 2014-05-18 02:54:23 +09:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2014-04-30 15:40:54 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2014-04-30 15:40:54 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2014-04-30 15:40:54 +02:00
.fbfilter.xml Update license headers 2012-06-04 13:31:44 -07: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 Preparation for porting OpenSSL support in 3.10 2014-05-17 20:01:47 +09:00
pom.xml Require Maven 3.1.1 or above 2014-06-04 03:15:38 +09:00
README.md Update README.md 2014-01-16 14:38:36 +09:00
run-example.sh Use a forked exec-maven-plugin instead of maven-antrun-plugin 2014-05-23 20:06:12 +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.