HTTP requests limitation for an Ethereum Node

Question

I have a fully synced Binance smart chain node with a proxy_pass to nginx for external request.

The problem that i have is the JSON-RPC return "null" if i process a large amount of requests.

For example : If i process 5000 rq/sec, i will got "null" response for about 30 %. (Basic request like eth_getBlockByNumber or eth_getTransactionReceipt).

Server :

AMD Ryzen 7 3800X - 8c/16t - 3.9 GHz/4.5 GHz
64 GB ECC 2666 MHz
2×960 GB SSD NVMe in RAID 0
Bandwidth 250 Mbps Up/250 Mbps Down (tested)

Config.toml modifications:

NoPruning = true
MaxPeers = 1000

Nginx setup :

Server :

location = /node {
    proxy_pass http://127.0.0.1:8080/;
}

Nginx.conf

events {
        worker_connections 6000;
        # multi_accept on;
}

I didn't found anything weird in the logs of nginx or in the node log.

I wonder if is there any limitations built in Ethereum nodes or others thinks like that ...

Thanks in advance.

Answer 1

After a lot of research, i found that nginx "reset connections" after 60 seconds.

When i reviews the configuration of reverse proxy, i found that i set this parameters that cause the problem :

location / {
    proxy_pass             http://127.0.0.1:8545;
    proxy_read_timeout     60;
    proxy_connect_timeout  60;
    proxy_redirect         off;
}

So, i delete all and i kept only proxy_pass and the problem was gone.

location / {
    proxy_pass             http://127.0.0.1:8545;
}

Thanks @ismael for your help.