In order to de-risk the rollout of the Netty 4 upgrade, we're starting out with the unpooled allocator. This was actually very helpful for digging into this issue since a full GC should have been able to reclaim most of the NIO memory.
We plan to transition to the pooled allocator once we shake out any other issues in the upgrade. Hopefully this is the last of those! On Mon, Jul 25, 2016 at 3:21 PM, 'Norman Maurer' via Netty discussions < [email protected]> wrote: > Something unrelated but why you use the UnpooledByteBufAllocator and not > the PooledByteBufAllocator ? > > > On 25 Jul 2016, at 20:43, Chris Conroy <[email protected]> wrote: > > > On Mon, Jul 25, 2016 at 2:35 PM, 'Norman Maurer' via Netty discussions < > [email protected]> wrote: > >> At the moment these Recyclers are not point to an EventLoopGroup as these >> are no even aware of anything like EventLoops. For example you may use >> buffers without EventLoops at all. >> > > This would be a bit easier to configure safe automatic defaults if it were >> a global (instead of per thread) recycler. How crazy would that be? Without >> that, the recyclers need to be small enough to multiply per thread in the >> app or there needs to be some kind of coordination mechanism to disable >> recycler growth in some threads if other threads are currently using a lot >> of capacity. There also might be some value in expiring older buffers so >> that after high pressure periods they are able to be reclaimed (I have had >> success doing this in MRU object pools elsewhere) >> >> >> So you are talking about automatically drop stuff if its not used for X >> timeframe ? >> > > Exactly! This works best if the pool is MRU retrieval instead of LRU or > random access retrieval. > > -- > You received this message because you are subscribed to the Google Groups > "Netty discussions" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/netty/CA%2B%3DgZKC_f80VxeZOryQcOPHSZGEBLf0SuG6YS0eWx7T86%2Bb6zA%40mail.gmail.com > <https://groups.google.com/d/msgid/netty/CA%2B%3DgZKC_f80VxeZOryQcOPHSZGEBLf0SuG6YS0eWx7T86%2Bb6zA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Netty discussions" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/netty/Ve4lnRvFXjM/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/netty/A7B9770D-8385-4CFB-9D35-93DED749F1F2%40googlemail.com > <https://groups.google.com/d/msgid/netty/A7B9770D-8385-4CFB-9D35-93DED749F1F2%40googlemail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Netty discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/netty/CA%2B%3DgZKATkid8smJ_kRdPHKufpvvP_HThGLCcDWmbi66zRXYbww%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
