[9] PING: RFC on 8165823 & 8168500: (se) EPollArrayWrapper optimization for large file descriptors

Brian Burkhalter brian.burkhalter at oracle.com
Sat Nov 5 19:15:01 UTC 2016


This post follows from the incomplete thread [1] regarding issue [2].

A request for more information was sent on Oct. 6 to the original submitter of [2] and the issue was marked as Resolved-Incomplete. The information requested was whether the file descriptor number resource limit could change dynamically in the submitter’s execution environment. As of now, no response has yet been received. Another issue [3] was filed so as not to lose track of the problem in case [2] remains incomplete.

Two solutions [4, 5] were proposed. Solution [4] removes initialization of the eventsHigh map based on resource limits in the EPollArrayWrapper constructor in favor of creating the map lazily if it is actually needed. Solution [5] always initializes the eventsHigh map during EPollArrayWrapper instantiation on the basis that this is simpler and has extremely low impact on performance and footprint.

My question here is whether either of the proposed solutions [4, 5] would be acceptable, an alternative solution should be investigated, or the topic abandoned until some future date?

Thanks,

Brian

[1] http://mail.openjdk.java.net/pipermail/nio-dev/2016-October/003896.html
[2] https://bugs.openjdk.java.net/browse/JDK-8165823
[3] https://bugs.openjdk.java.net/browse/JDK-8168500
[4] http://cr.openjdk.java.net/~bpb/8165823/webrev.00/
[5] http://mail.openjdk.java.net/pipermail/nio-dev/2016-October/003947.html


More information about the nio-dev mailing list