Show HN: Multi process twemproxy with config reload online

Show HN: Multi process twemproxy with config reload online

However, with a large mbuf size, every active connection would use up 16K bytes of buffer which might be an issue when twemproxy is handling large number of concurrent connections from clients. When twemproxy is meant to handle a large number of concurrent client connections, you should set chunk size to a small value like 512 bytes using the -m or –mbuf-size=N argument. For example, if twemproxy is proxying three client connections onto a single server and we get requests – ‘get key\r

‘, ‘set key 0 0 3\r

val\r

‘ and ‘delete key\r

‘ on these three connections respectively, twemproxy would try to batch these requests and send them as a single message onto the server connection as ‘get key\r

set key 0 0 3\r

val\r

delete key\r

‘.

Source: github.com