root
3e7ddb36c7
[maven-release-plugin] prepare for next development iteration
2018-10-29 15:38:51 +00:00
root
9e50739601
[maven-release-plugin] prepare release netty-4.1.31.Final
2018-10-29 15:37:47 +00:00
root
2d7cb47edd
[maven-release-plugin] prepare for next development iteration
2018-09-27 19:00:45 +00:00
root
3a9ac829d5
[maven-release-plugin] prepare release netty-4.1.30.Final
2018-09-27 18:56:12 +00:00
root
a580dc7585
[maven-release-plugin] prepare for next development iteration
2018-08-24 06:36:33 +00:00
root
3fc789e83f
[maven-release-plugin] prepare release netty-4.1.29.Final
2018-08-24 06:36:06 +00:00
root
fcb19cb589
[maven-release-plugin] prepare for next development iteration
2018-07-27 04:59:28 +00:00
root
ff785fbe39
[maven-release-plugin] prepare release netty-4.1.28.Final
2018-07-27 04:59:06 +00:00
root
b4dbdc2036
[maven-release-plugin] prepare for next development iteration
2018-07-11 15:37:40 +00:00
root
1c16519ac8
[maven-release-plugin] prepare release netty-4.1.27.Final
2018-07-11 15:37:21 +00:00
root
7bb9e7eafe
[maven-release-plugin] prepare for next development iteration
2018-07-10 05:21:24 +00:00
root
8ca5421bd2
[maven-release-plugin] prepare release netty-4.1.26.Final
2018-07-10 05:18:13 +00:00
Norman Maurer
64bb279f47
[maven-release-plugin] prepare for next development iteration
2018-05-14 11:11:45 +00:00
Norman Maurer
c67a3b0507
[maven-release-plugin] prepare release netty-4.1.25.Final
2018-05-14 11:11:24 +00:00
Norman Maurer
b75f44db9a
[maven-release-plugin] prepare for next development iteration
2018-04-19 11:56:07 +00:00
Norman Maurer
04fac00c8c
[maven-release-plugin] prepare release netty-4.1.24.Final
2018-04-19 11:55:47 +00:00
root
0a61f055f5
[maven-release-plugin] prepare for next development iteration
2018-04-04 10:44:46 +00:00
root
8c549bad38
[maven-release-plugin] prepare release netty-4.1.23.Final
2018-04-04 10:44:15 +00:00
Norman Maurer
69582c0b6c
[maven-release-plugin] prepare for next development iteration
2018-02-21 12:52:33 +00:00
Norman Maurer
786f35c6c9
[maven-release-plugin] prepare release netty-4.1.22.Final
2018-02-21 12:52:19 +00:00
Norman Maurer
e71fa1e7b6
[maven-release-plugin] prepare for next development iteration
2018-02-05 12:02:35 +00:00
Norman Maurer
41ebb5fcca
[maven-release-plugin] prepare release netty-4.1.21.Final
2018-02-05 12:02:19 +00:00
Norman Maurer
ea58dc7ac7
[maven-release-plugin] prepare for next development iteration
2018-01-21 12:53:51 +00:00
Norman Maurer
96c7132dee
[maven-release-plugin] prepare release netty-4.1.20.Final
2018-01-21 12:53:34 +00:00
Norman Maurer
264a5daa41
[maven-release-plugin] prepare for next development iteration
2017-12-15 13:10:54 +00:00
Norman Maurer
0786c4c8d9
[maven-release-plugin] prepare release netty-4.1.19.Final
2017-12-15 13:09:30 +00:00
Norman Maurer
b2bc6407ab
[maven-release-plugin] prepare for next development iteration
2017-12-08 09:26:15 +00:00
Norman Maurer
96732f47d8
[maven-release-plugin] prepare release netty-4.1.18.Final
2017-12-08 09:25:56 +00:00
Norman Maurer
188ea59c9d
[maven-release-plugin] prepare for next development iteration
2017-11-08 22:36:53 +00:00
Norman Maurer
812354cf1f
[maven-release-plugin] prepare release netty-4.1.17.Final
2017-11-08 22:36:33 +00:00
Norman Maurer
625a7426cd
[maven-release-plugin] prepare for next development iteration
2017-09-25 06:12:32 +02:00
Norman Maurer
f57d8f00e1
[maven-release-plugin] prepare release netty-4.1.16.Final
2017-09-25 06:12:16 +02:00
Norman Maurer
b967805f32
[maven-release-plugin] prepare for next development iteration
2017-08-24 15:38:22 +02:00
Norman Maurer
da8e010a42
[maven-release-plugin] prepare release netty-4.1.15.Final
2017-08-24 15:37:59 +02:00
Norman Maurer
52f384b37f
[maven-release-plugin] prepare for next development iteration
2017-08-02 12:55:10 +00:00
Norman Maurer
8cc1071881
[maven-release-plugin] prepare release netty-4.1.14.Final
2017-08-02 12:54:51 +00:00
Norman Maurer
2a376eeb1b
[maven-release-plugin] prepare for next development iteration
2017-07-06 13:24:06 +02:00
Norman Maurer
c7f8168324
[maven-release-plugin] prepare release netty-4.1.13.Final
2017-07-06 13:23:51 +02:00
Norman Maurer
fd67a2354d
[maven-release-plugin] prepare for next development iteration
2017-06-08 21:06:24 +02:00
Norman Maurer
3acd5c68ea
[maven-release-plugin] prepare release netty-4.1.12.Final
2017-06-08 21:06:01 +02:00
Norman Maurer
0db2901f4d
[maven-release-plugin] prepare for next development iteration
2017-05-11 16:00:55 +02:00
Norman Maurer
f7a19d330c
[maven-release-plugin] prepare release netty-4.1.11.Final
2017-05-11 16:00:16 +02:00
Norman Maurer
6915ec3bb9
[maven-release-plugin] prepare for next development iteration
2017-04-29 14:10:00 +02:00
Norman Maurer
f30f242fee
[maven-release-plugin] prepare release netty-4.1.10.Final
2017-04-29 14:09:32 +02:00
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
