RE: Long duration of close(socket) and signal problem

> > To my great surprise, the close(socket) operation > > took EXTREMELY long. It > > took 0.11 second (CPU usage was low), while this > > operation under MinGW 1.1 > > on the same machine took only 0.00019 second. On > > another Linux machine, > > close took 0.43 second. > > A solution may be

RE: Long duration of close(socket) and signal problem

> To my great surprise, the close(socket) operation > took EXTREMELY long. It > took 0.11 second (CPU usage was low), while this > operation under MinGW 1.1 > on the same machine took only 0.00019 second. On > another Linux machine, > close took 0.43 second. > An strace of fakeweb with a patch

Long duration of close(socket) and signal problem

To compare the network performance of Cygwin and native WinSock, I wrote the attached code. Under the three compiler (MinGW 1.1 GCC 2.95, Cygwin GCC 2.95, GCC 2.96 of Red Hat 7.1) I used, I typed only "gcc -Wall fakeweb.c -o fakeweb" to build. Then I used a Web stress tool to send HTTP GET reques