andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
5,693 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
9c934116f2
Go to file
Norman Maurer 9c934116f2 [#2370] Periodically check for not alive Threads and free up their ThreadPoolCache 
Motivation:
At the moment we create new ThreadPoolCache whenever a Thread tries either allocate or release something on the PooledByteBufAllocator. When something is released we put it then in its ThreadPoolCache. The problem is we never check if a Thread is not alive anymore and so we may end up with memory that is never freed again if a user create many short living Threads that use the PooledByteBufAllocator.

Modifications:
Periodically check if the Thread is still alive that has a ThreadPoolCache assinged and if not free it.

Result:
Memory is freed up correctly even for short living Threads.
2014-04-09 11:44:51 +02:00
all [maven-release-plugin] prepare for next development iteration 2014-04-01 07:21:40 +02:00
buffer [#2370] Periodically check for not alive Threads and free up their ThreadPoolCache 2014-04-09 11:44:51 +02:00
codec [#2353] Use a privileged block to get ClassLoader and System property if needed 2014-04-08 13:59:03 +02:00
codec-http [maven-release-plugin] prepare for next development iteration 2014-04-01 07:21:40 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2014-04-01 07:21:40 +02:00
common [#2353] Use a privileged block to get ClassLoader and System property if needed 2014-04-08 13:59:03 +02:00
example [#2353] Use a privileged block to get ClassLoader and System property if needed 2014-04-08 13:59:03 +02:00
handler [#2353] Use a privileged block to get ClassLoader and System property if needed 2014-04-08 13:59:03 +02:00
license [#1259] Add optimized queue for SCMP pattern and use it in NIO and native transport 2014-02-27 11:44:06 +01:00
microbench [maven-release-plugin] prepare for next development iteration 2014-04-01 07:21:40 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2014-04-01 07:21:40 +02:00
testsuite [maven-release-plugin] prepare for next development iteration 2014-04-01 07:21:40 +02:00
transport [#2353] Use a privileged block to get ClassLoader and System property if needed 2014-04-08 13:59:03 +02:00
transport-native-epoll [#2353] Use a privileged block to get ClassLoader and System property if needed 2014-04-08 13:59:03 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2014-04-01 07:21:40 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2014-04-01 07:21:40 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2014-04-01 07:21:40 +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 Format and partially describe Gitignore 2013-12-10 07:04:38 +01: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 [#1259] Add optimized queue for SCMP pattern and use it in NIO and native transport 2014-02-27 11:44:06 +01:00
pom.xml [maven-release-plugin] prepare for next development iteration 2014-04-01 07:21:40 +02:00
README.md Update README.md 2014-01-16 14:38:36 +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.