Windows – How to set maximum queue connection for nginx port in Windows

nginxwindows

I am learning to design scalable system, for now using Windows machine. I created two servers that will listen to port 27016 and 27015, all they do is return "HelloWorld!" response. I had set listen(ListenSocket, SOMAXCONN) for both the servers when creating them in Visual studio following Winsock tutorial. Using jmter performed load test on each of them individually (1000 request per sec) and got everything OK.

Now when I introduced nginx which is listening to port 80 and load balancing the requests (1000 req per sec) among the two servers I mentioned above, many requests are being dropped down while performing load test using jmeter.

I am assuming that queue size for port 80 is not configured for high traffic and want to tune it. How to set the queue size to maximum possible value either from nginx config or cmd command?

Best Answer

Here is the information from Nginx web site:

worker_processes: The number of NGINX worker processes (the default is 1). In most cases, running one worker process per CPU core works well, and we recommend setting this directive to auto to achieve that. There are times when you may want to increase this number, such as when the worker processes have to do a lot of disk I/O.

worker_connections: The maximum number of connections that each worker process can handle simultaneously. The default is 512, but most systems have enough resources to support a larger number. The appropriate setting depends on the size of the server and the nature of the traffic, and can be discovered through testing.

So, the best choice for worker_processes is the same as the number of cores you have. And the value or worker_connections defaults to 512. You can increase it depending on your needs, and as your system can handle.

The following could be helpfull too:

keepalive_requests : The number of requests a client can make over a single keepalive connection. The default is 100, but a much higher value can be especially useful for testing with a load‑generation tool, which generally sends a large number of requests from a single client.

keepalive_timeout : How long an idle keepalive connection remains open. The following directive relates to upstream keepalives:

keepalive : The number of idle keepalive connections to an upstream server that remain open for each worker process. There is no default value.

I hope this will helps!

Note: I agree with @Alexey Ten

Related Solutions

Windows – How to find what process is holding a file open in Windows

I've had success with Sysinternals Process Explorer. With this, you can search to find what process(es) have a file open, and you can use it to close the handle(s) if you want. Of course, it is safer to close the whole process. Exercise caution and judgement.

To find a specific file, use the menu option Find->Find Handle or DLL... Type in part of the path to the file. The list of processes will appear below.

If you prefer command line, Sysinternals suite includes command line tool Handle, that lists open handles.

Examples

c:\Program Files\SysinternalsSuite>handle.exe |findstr /i "e:\" (finds all files opened from drive e:\"
c:\Program Files\SysinternalsSuite>handle.exe |findstr /i "file-or-path-in-question"

Nginx and Apache – Using Nginx for Static Files and Apache for Dynamic Content

They can be on the same port, if they are on different IPs. Or they can be on different ports with the same IP, just not both (Could also be different IPs and Different Ports). The multiple IP scenario is required if they will be different servers, but you could use multiple IPs on the same server.

I swear I am not trying to confuse you :-)

The location directive in the link you provided would go within the server directive (Notice that in the documentation for the location directive there is "context: server "). If you are using a recent Ubuntu version with a default apt install, you probably want to edit default in the sites-enabled directory. For example (kind of silly since it passes everything to Apache):

server {
    listen   80 default;

    access_log  /var/log/nginx/localhost.access.log;

    location / {
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_pass http://localhost:2500;
    }
}

In this case I am using the same server for both. Nginx listens on 80, and Apache Listens on 2500. You would point DNS to the ip of the Nginx server since that is the one that handles all requests by proxying for the other servers. Basically, from the client perspective, they are only talking to the Nginx server.

Best Answer

Related Solutions

Windows – How to find what process is holding a file open in Windows

Nginx and Apache – Using Nginx for Static Files and Apache for Dynamic Content

Related Topic