I think 50000 msg/s is good enough. I used to make performance test on Redis and memcached. Redis can reach 72000 msg/s, memcached can reach 25000 msg/s. The speed of request/reply pattern is limited by the round trip cost of TCP. If we want much higher qps, I think we should use asynchronous pattern, in which the users can register a callback function for request and pick the corresponding response when it arrived. On Tue, Jan 20, 2015 at 4:03 PM, Pierre Salmon <pierre.salmon@xxxxxxxxxxxxx> wrote: > For information, I already implemented this example and i obtained only > 50000 msg/s. > > Pierre > > > On 01/20/2015 03:37 AM, Garrett D'Amore wrote: > >> socket used by the worker. That means you have to save the header and >> restore it — the device() routine has this logic, but you need to copy that >> logic as appropriate, rat >> > > >