Bug#988191: ionos-1 proxy causes lots of temporary build failures by being slow to respond

Helmut Grohne helmut at subdivi.de
Fri May 7 12:50:04 BST 2021


Hi Holger,

On Fri, May 07, 2021 at 11:32:21AM +0000, Holger Levsen wrote:
> as a simple fix: we could install squid on your node (ionos9?) and a another
> cpu for it? (and 4gb ram or such)

I'm unsure what you mean here precisely. Do you mean adding a separate
squid on ionos9 used by only ionos9 or do you mean moving the squid from
ionos1 to ionos9 and moving all of its users over to ionos9?

Both seem sensible to me, but the resource adjustments are slightly
different in each case.

If the proxy is only used locally, adding another cpu is unnecessary as
the times when the proxy is being used we are not cpu bound. Adding a
bit of ram for that case sounds sensible though 2gb should already
suffice in that case.

If other the other nodes from the same datacenter are supposed to use
the moved proxy, your adjustments seem sensible to me. Note that ionos9
intentionally swaps a lot. The swapping is a lot less bursty and a
magnitude lower than that observed on ionos1, but we may have to apply
resource limits to keep the proxy responsive.

Possibly adding a bit of disk space for the squid spool (20G?) would
be necessary to avoid excessive refetching.

Helmut



More information about the Qa-jenkins-dev mailing list