Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Netty default allocator whenever it is pooled otherwise fallback to adaptive allocator #5379

Merged
merged 1 commit into from
Nov 5, 2024

Conversation

vietj
Copy link
Member

@vietj vietj commented Oct 29, 2024

Motivation:

Vert.x should use Netty's default allocator whenever possible in order to minimize the resources for pooled allocation (thread-local direct buffers, arenas).

Changes:

VertxByteBufAllocator.POOLED_ALLOCATOR reuses ByteBufAllocator.DEFAULT when it is pooled otherwise uses AdaptiveByteBufAllocator.DEFAULT.

TCP server/client should use VertxByteBufAllocator.POOLED_ALLOCATOR instead of PooledByteBufAllocator.DEFAULT.

@vietj vietj changed the title Use Netty default allocator whenever it is pooled otherwise fallback to adapative allocator Use Netty default allocator whenever it is pooled otherwise fallback to adaptive allocator Oct 29, 2024
@vietj vietj added this to the 5.0.0 milestone Oct 29, 2024
@vietj vietj force-pushed the unified-pooled-allocator branch 4 times, most recently from c446d7c to f118709 Compare October 29, 2024 14:35
@vietj vietj self-assigned this Oct 29, 2024
…to adaptive allocator.

Motivation:

Vert.x should use Netty's default allocator whenever possible in order to minimize the resources for pooled allocation (thread-local direct buffers, arenas).

Changes:

VertxByteBufAllocator.POOLED_ALLOCATOR reuses ByteBufAllocator.DEFAULT when it is pooled otherwise uses AdaptiveByteBufAllocator.DEFAULT.

TCP server/client should use VertxByteBufAllocator.POOLED_ALLOCATOR instead of PooledByteBufAllocator.DEFAULT.
@vietj vietj merged commit 02316d5 into master Nov 5, 2024
8 checks passed
@vietj vietj deleted the unified-pooled-allocator branch November 5, 2024 15:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants