I managed to get better performance by doing the following changes:
* Increasing apache parameters 'ServerLimit' and 'MaxRequestWorkers'. This
was suggested from warning in the apache error logs which I had missed.
* Increasing aiohttpd workers for the pulpcore-content service from 2 to 6.
Not sure what effect if any this has.
Not sure which measure had effect or if it is a combination, but things seem to
run pretty smoothly now without any errors. Still not quite as fast as with
pulp2, so if anyone has any tips I'll gladly accept them.
//Adam
From: pulp-list-boun...@redhat.com on behalf of
Winberg Adam
Sent: 20 January 2021 15:38
To: pulp-list@redhat.com
Subject: [Pulp-list] very slow yum runs
Hello,
we have been using a pulp2 installation serving yum repos to ~ 1200 clients.
Yesterday I went live with a pulp3 installation and client yum runs was very
slow. I mean timeout-slow, grinding our puppet runs to a halt and forcing me to
revert back to our pulp2 instance.
Pulp3 is behind a apache reverse proxy, and I'm seeing errors like:
AH01102: error reading status line from remote server 127.0.0.1:24816
There is no shortage of cpu/ram on the server. Pulp is connected to a remote
postgresql server.
Using rpm based installation on RHEL8 with
python3-pulp-rpm-3.7.0-1.el8.noarch
python3-pulpcore-3.7.3-1.el8.noarch
Anyone recognize this problem, is there some basic tuning that I have missed?
Regards
Adam
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list