René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Netty 4.2 series and the adaptive allocator.","articleBody":"Netty 4.2 introduces a new default buffer allocator - see the [migration guide](https://github.com/netty/netty/wiki/Netty-4.2-Migration-Guide) and in particular:\n\n\u003e Netty 4.2 changes the default allocator to adaptive. To de-risk this change, it is recommended to first upgrade to 4.2 while explicitly configuring the pooled allocator, and then remove the allocator configuration as a second step. To explicitly configure the pooled allocator, set this system property: io.netty.allocator.type=pooled\n\nI have confirmed that in my codebase using lmdbjava, setting the system property means lmdbjava continues to work with netty 4.2.\n\nMy inclination would be to add a new buffer proxy PROXY_NETTY_ADAPTIVE, rename the older proxy to PROXY_NETTY_POOLED and for backwards compatibility keep PROXY_NETTY. The latter could default to the same as PROXY_NETTY_POOLED or attempt to choose the default  based on netty version (Netty does provide a Version class so this could be determined at runtime and cached but with some added complexity obviously).\n\nI asked Claude to help with this, and I will append its response in a separate message. \n\nWhat do people think of this idea? \n\nWould there be an appetite to look at a PR to add netty 4.2 support? This would allow performance testing of the new adaptive allocator?\n\n\n\n","author":{"url":"https://github.com/wardle","@type":"Person","name":"wardle"},"datePublished":"2025-10-25T17:03:40.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/261/lmdbjava/issues/261"}