Go to file
Jason Tedor 98beb777f8 Enable configuring available processors
Motivation:

In cases when an application is running in a container or is otherwise
constrained to the number of processors that it is using, the JVM
invocation Runtime#availableProcessors will not return the constrained
value but rather the number of processors available to the virtual
machine. Netty uses this number in sizing various resources.
Additionally, some applications will constrain the number of threads
that they are using independenly of the number of processors available
on the system. Thus, applications should have a way to globally
configure the number of processors.

Modifications:

Rather than invoking Runtime#availableProcessors, Netty should rely on a
method that enables configuration when the JVM is started or by the
application. This commit exposes a new class NettyRuntime for enabling
such configuraiton. This value can only be set once. Its default value
is Runtime#availableProcessors so that there is no visible change to
existing applications, but enables configuring either a system property
or configuring during application startup (e.g., based on settings used
to configure the application).

Additionally, we introduce the usage of forbidden-apis to prevent future
uses of Runtime#availableProcessors from creeping. Future work should
enable the bundled signatures and clean up uses of deprecated and
other forbidden methods.

Result:

Netty can be configured to not use the underlying number of processors,
but rather the constrained number of processors.
2017-04-23 10:31:17 +02: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-03-10 07:46:17 +01:00
bom [maven-release-plugin] prepare for next development iteration 2017-03-10 07:46:17 +01:00
buffer Enable configuring available processors 2017-04-23 10:31:17 +02:00
codec Fix possible overflow when calculate in the size of the out buffer in Base64 2017-04-21 08:11:17 +02:00
codec-dns fix the typos 2017-04-20 04:56:09 +02:00
codec-haproxy fix the typos 2017-04-20 04:56:09 +02:00
codec-http fix the typos 2017-04-20 04:56:09 +02:00
codec-http2 Fix HTTP/2 dependency tree corruption 2017-04-22 08:26:47 -07:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2017-03-10 07:46:17 +01:00
codec-mqtt fix the typos 2017-04-20 04:56:09 +02:00
codec-redis fix the typos 2017-04-20 04:56:09 +02:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2017-03-10 07:46:17 +01:00
codec-socks fix the typos 2017-04-20 04:56:09 +02:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2017-03-10 07:46:17 +01:00
codec-xml [maven-release-plugin] prepare for next development iteration 2017-03-10 07:46:17 +01:00
common Enable configuring available processors 2017-04-23 10:31:17 +02:00
dev-tools Enable configuring available processors 2017-04-23 10:31:17 +02:00
example fix the typos 2017-04-20 04:56:09 +02:00
handler #6657 do not throw ClassCastException when rule subnet version doesn't match remote IP version 2017-04-23 08:30:02 +02:00
handler-proxy fix the typos 2017-04-20 04:56:09 +02: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 fix the typos 2017-04-20 04:56:09 +02:00
resolver [maven-release-plugin] prepare for next development iteration 2017-03-10 07:46:17 +01:00
resolver-dns Regulation of the InternetProtocolFamily usage 2017-04-20 05:22:24 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2017-03-10 07:46:17 +01:00
testsuite fix the typos 2017-04-20 04:56:09 +02:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2017-03-10 07:46:17 +01:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2017-03-10 07:46:17 +01:00
transport Enable configuring available processors 2017-04-23 10:31:17 +02:00
transport-native-epoll [maven-release-plugin] prepare for next development iteration 2017-03-10 07:46:17 +01:00
transport-rxtx fix the typos 2017-04-20 04:56:09 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2017-03-10 07:46:17 +01:00
transport-udt fix the typos 2017-04-20 04:56:09 +02: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 Enable configuring available processors 2017-04-23 10:31:17 +02:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:08:01 +01:00
run-example.sh Add an example client for codec-redis 2016-04-23 11:18:12 -07: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.