Hi František, On Thu, Oct 20, 2022 at 08:30:23PM +0200, František Šumšal wrote: > I originally reported it to the CentOS Infra tracker [0] but was > advised to post it here, since this behavior is, for better or worse, > expected, or at least that's how the T2 machines are advertised. Is > there anything that can be done to mitigate this? The only available > solution would be to move the job back to the metal nodes, but that's > going against the original issue (and the metal pool is quite limited > anyway). T2 instances don't have to be rate limited if you are ready to pay for it: iiuc the T2 unlimited mode [1] allows you to trade higher CPU utilization for money. Cheers Michael [1] https://aws.amazon.com/blogs/aws/new-t2-unlimited-going-beyond-the-burst-with-high-performance/ > [0] https://pagure.io/centos-infra/issue/950 -- Michael Hofmann (he/him) | CKI | IRC mh21 #kernelci | GPG 0xE8E1F78D86F24DA1 Red Hat GmbH, Werner von Siemens Ring 12, D-85630 Grasbrunn Amtsgericht Muenchen/Munich, HRB 153243 Managing Directors: Ryan Barnhart, Charles Cachera, Michael O'Neill, Amy Ross -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <http://lists.centos.org/pipermail/ci-users/attachments/20221020/18a0abb5/attachment-0002.sig>