Skip to content

Forward port 5.0: Remove the unpooled allocator from test permutations#16289

Merged
chrisvest merged 1 commit into5.0from
forwardport-pr-16282-to-5.0
Feb 17, 2026
Merged

Forward port 5.0: Remove the unpooled allocator from test permutations#16289
chrisvest merged 1 commit into5.0from
forwardport-pr-16282-to-5.0

Conversation

@netty-project-bot
Copy link
Copy Markdown
Contributor

Forward port of #16282 to 5.0
Cherry-picked commit: 8987ec5


Motivation:
The unpooled allocator will allocate and deallocate memory for each buffer, rather than pool the memory. On Java 25+, deallocating memory (in the form of shared memory segments) involves thread-local handshakes, and can have significant overhead to the point of causing frequent test timeouts. Additionally, having the unpooled allocator in the test permutations does not add very much to test coverage.

Modification:
Remove the unpooled allocator from the transport test permutation parameters.

Result:
Much faster builds, from removing the overhead of releasing millions of shared memory segments.

Motivation:
The unpooled allocator will allocate and deallocate memory for each
buffer, rather than pool the memory. On Java 25+, deallocating memory
(in the form of shared memory segments) involves thread-local
handshakes, and can have significant overhead to the point of causing
frequent test timeouts. Additionally, having the unpooled allocator in
the test permutations does not add very much to test coverage.

Modification:
Remove the unpooled allocator from the transport test permutation
parameters.

Result:
Much faster builds, from removing the overhead of releasing millions of
shared memory segments.

(cherry picked from commit 8987ec5)
@chrisvest chrisvest enabled auto-merge (squash) February 17, 2026 19:43
@chrisvest chrisvest added this to the 5.0.0.Final milestone Feb 17, 2026
@chrisvest chrisvest merged commit 9759a4a into 5.0 Feb 17, 2026
13 checks passed
@chrisvest chrisvest deleted the forwardport-pr-16282-to-5.0 branch February 17, 2026 21:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants