Join GitHub today
Please provide real benchmark data and sever information. #4
The claim for 1m concurrent connections is a pretty big one. Please provide the following:
My initial tests show there is alot of failures, with only 100 concurrents and 5 req per sec - throughput drops by 8% (unacceptable) and siege fails.
Seems like averaging 1800 req/sec which is only 4x better than
Any idea? Perhaps provide some sample code for me to test with.
In my sample code I am using
1M concurrent connections with 100k rps were achieved in production, not in test environment. The server had the following configuration:
Long-living keep-alive connections are established by video clients all over the world. Clients periodically send event requests to the server over these connections. The server pushes event data to db and sends back just transparent pixel. Every client sends an event every 10 seconds on average.
Less than 100ms from the client side.
The main bottleneck was 1Gbit network, so we moved to 10Gbit :)
We moved to 32-CPU, 128GB RAM, 10Gbit server now. Preliminary results show that the server could handle over 500K rps. Unfortunately we have no 5M concurrent clients yet for testing such a load :(
The rps seems too low for both net/http and fasthttp. Maybe your request handler is too heavy. See sample code from the pull request to TechEmpower benchmarks.