heap size limited service to send large object, recommend configuration for pool buffer allocator?

17 views

Skip to first unread message

yang ye

unread,

Nov 10, 2017, 1:09:14 PM11/10/17

to Netty discussions

Hi Team,

I'm working on a service that is very limited and concerned on the heap size (only 128MB). Its main task is just to send out files with size normally ranging from several KB to 100 MB.

I used the async http client (2.0.31) with netty (4.0.45 final) built-in. By default, the ahc uses the unpooled buffer allocator. But the GC got triggered a lot during object sending. So I'm looking into the pooled buffer allocator.

Wondering any recommendation on the chunk size, page size, max order and other configuration I can try with? Any other recommendations are so welcome!