<html><head><title></title></head><body><div class="rte-style-maintainer rte-pre-wrap" data-color="global-default" bbg-color="default" data-bb-font-size="medium"bbg-font-size="medium" style="white-space: pre-wrap; font-size: small; font-family: "Courier New", Courier, "BB.FixedWidth";"style="white-space: pre-wrap; font-size: small; font-family: "Courier New", Courier, "BB.FixedWidth"; color: rgb(0, 0, 0);">We recently add more clients to use the pulp content server. The processes run out the file descriptor first. We then increased both nginx and pulp-content by creating a override.conf <div>/etc/systemd/system/pulpcore-content.service.d # cat override.conf </div><div>[Service]</div><div>LimitNOFILE=65536</div><div><br><div>and updated nginx.conf</div><div># Gunicorn docs suggest this value.</div><div>worker_processes 1;</div><div>events {</div><div> worker_connections 10000; # increase if you have lots of clients</div><div> accept_mutex off; # set to 'on' if nginx worker_processes > 1</div><div>}</div><div><br></div><div>worker_rlimit_nofile 20000;</div><div><br></div><div><br></div><div>Now we are keep getting this error.</div></div><div>2021/06/22 11:26:36 [error] 78373#0: *112823 upstream timed out (110: Connection timed out) while connecting to upstream, client:</div><div><br></div><div>It looks like pulp-content server cannot keep up with requests. Is there anything we could do to increase the performance of the content server?</div></div></body></html>