We've been working on efficiency and performance over the past few releases, particularly the one that will be releasing in the next week (3.14). I wouldn't expect that changing the number of Nginx workers would improve anything, but improving the number of gunicorn workers *should*. It sounds like you may have already done that?
In pulpcore-content.service, tweak the value of "workers": ExecStart=/usr/local/lib/pulp/bin/gunicorn pulpcore.content:server \ > --bind '127.0.0.1:24816' \ > --worker-class 'aiohttp.GunicornWebWorker' \ > --workers 8 \ > --timeout 90 \ > --access-logfile - > But yes, this is a brute force approach, for better efficiency you'll need to upgrade. On Tue, Jun 22, 2021 at 11:34 AM Bin Li (BLOOMBERG/ 120 PARK) < [email protected]> wrote: > 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 > /etc/systemd/system/pulpcore-content.service.d # cat override.conf > [Service] > LimitNOFILE=65536 > > and updated nginx.conf > # Gunicorn docs suggest this value. > worker_processes 1; > events { > worker_connections 10000; # increase if you have lots of clients > accept_mutex off; # set to 'on' if nginx worker_processes > 1 > } > > worker_rlimit_nofile 20000; > > > Now we are keep getting this error. > 2021/06/22 11:26:36 [error] 78373#0: *112823 upstream timed out (110: > Connection timed out) while connecting to upstream, client: > > 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? > _______________________________________________ > Pulp-list mailing list > [email protected] > https://listman.redhat.com/mailman/listinfo/pulp-list
_______________________________________________ Pulp-list mailing list [email protected] https://listman.redhat.com/mailman/listinfo/pulp-list
