Re: TCP server app performance

2018-08-15 Thread Michio Honda
On 08/14/2018 09:30 PM, Navdeep Parhar wrote: On 8/12/18 9:50 AM, Honda Michio wrote: Hi, I'm measuring TCP server app performance using my toy web server. It just accept TCP connections and responds back HTTP OK to the clients. It monitors sockets using kqueue, and processes each ready desc

Re: TCP server app performance

2018-08-14 Thread Navdeep Parhar
On 8/12/18 9:50 AM, Honda Michio wrote: > Hi, > > I'm measuring TCP server app performance using my toy web server. > It just accept TCP connections and responds back HTTP OK to the clients. > It monitors sockets using kqueue, and processes each ready descriptor using > a pair of read() and write(

Re: TCP server app performance

2018-08-12 Thread Matthias Apitz
El día domingo, agosto 12, 2018 a las 09:32:28p. m. +0200, Michio Honda escribió: > Hi Rozhuk, > > I only use a single CPU core and thread, so SO_REUSEPORT_LB has no > effect. Also, I already accept() in loop until getting error, but this > is not a point as I use persistent TCP connections...

Re: TCP server app performance

2018-08-12 Thread Michio Honda
Hi Rozhuk, I only use a single CPU core and thread, so SO_REUSEPORT_LB has no effect. Also, I already accept() in loop until getting error, but this is not a point as I use persistent TCP connections... Cheers, - Michio On 08/12/2018 07:50 PM, Rozhuk Ivan wrote: On Sun, 12 Aug 2018 18:50:1

Re: TCP server app performance

2018-08-12 Thread Rozhuk Ivan
On Sun, 12 Aug 2018 18:50:17 +0200 Honda Michio wrote: > I'm measuring TCP server app performance using my toy web server. > It just accept TCP connections and responds back HTTP OK to the > clients. It monitors sockets using kqueue, and processes each ready > descriptor using a pair of read() an

Re: TCP server app performance

2018-08-12 Thread Rozhuk Ivan
On Sun, 12 Aug 2018 18:50:17 +0200 Honda Michio wrote: > I'm measuring TCP server app performance using my toy web server. > It just accept TCP connections and responds back HTTP OK to the > clients. It monitors sockets using kqueue, and processes each ready > descriptor using a pair of read() an