[#2145] feat(server): The server-side supports choosing Netty's ByteBufAllocator.#2146
[#2145] feat(server): The server-side supports choosing Netty's ByteBufAllocator.#2146zhengchenyu wants to merge 1 commit intoapache:masterfrom
Conversation
… ByteBufAllocator
|
The Uniffle server does not support |
Test Results 2 744 files - 46 2 744 suites - 46 5h 8m 4s ⏱️ - 16m 25s For more details on these failures, see this check. Results for commit 84ab3d4. ± Comparison against base commit 8f4494b. |
Thanks for you quick reply! It is just a draft. |
|
Yes, you are right. |
Thanks for your reply! I will revert it in our repo, then I'm trying to use mimalloc that you talked about earlier. |
|
I need this feature. I found that in our production environment, memory allocation and deallocation are very slow on the machines with large memory(1.5T). We will reserve sufficient memory, so I think the risk of OOM is relatively low for us. So I think this feature can be used as an option. cc @rickyma @zhengchenyu @jerqi @zuston |
Make sense to me. Let @zhengchenyu take a deep look. |
What changes were proposed in this pull request?
The server-side supports choosing Netty's ByteBufAllocator.
Why are the changes needed?
Fix: #2145
Does this PR introduce any user-facing change?
Introduce rss.server.netty.pooled.allocator.enabled to choose allocator.
How was this patch tested?
test in cluster.