On úterý 22. listopadu 2022 19:21:01 CET Pavel Raiskup wrote:
On úterý 22. listopadu 2022 12:23:54 CET David Duncan wrote:
> > On pondělí 21. listopadu 2022 3:16:39 CET Neal Gompa wrote:
> >
> > Not sure what is in Koji, so just some facts about the Copr arm builders...
> >
> > Copr uses 'a1.2xlarge' machines:
> >
https://aws.amazon.com/ec2/instance-types/a1/
> >
>
> We do have access to the later generations: The [CMR]6g and then the latest
> Graviton 3 instances in the C7g family.
>
> Our (AWS’s) engineering team highly discourages the use of the a1 instance
> types at this point. Can we move that to standard T4g.2xl or better yet update
> that to a C6g.2xl?
I tested c6g and c7g today.
Note this is being tested on staging instance, with c7g.xlarge:
https://copr.stg.fedoraproject.org/coprs/praiskup/ping/build/2910412/
So the CPU count and RAM size stays:
https://pagure.io/fedora-infra/ansible/c/5023fd514222eb77e6b1fc0c3494aa5a...
If everything goes OK, we could have it in production next week.
Pavel
They seem to work, but subscription-manager seems to fail (some
entitlement issue). When we sort this out, it would be an easy switch,
thank you for the tip!
> It sounds like we need to update the infrastructure definitions to include the
> later versions. These next-generation instance types will definitely increase
> the efficiency of the workload.
They indeed are much faster.
> > Copr uses mock's tmpfs feature, with cca 140GB SWAP volume on a gp2 disk:
> >
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/general-purpose.html
> >
>
> Some of the justification should come directly from the ec2 optimizer in
> the account. We should probably take a look at the profile information
> there to determine what will be the best fit cost/performance wise.
Never used ec2 optimizer. Another very good tip, thanks.
Pavel