From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Thomas Huth" <thuth@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: s390 private runner CI job timing out
Date: Thu, 6 Apr 2023 13:17:45 +0200 [thread overview]
Message-ID: <149e9342-b48b-0871-ee4d-96c6f1d3f198@linux.ibm.com> (raw)
In-Reply-To: <CAFEAcA_Uh+20w1gnCBXe6Go9WqkUu+SUeRtsrrbwEO4j48OjGQ@mail.gmail.com>
Am 06.04.23 um 12:44 schrieb Peter Maydell:
> On Thu, 6 Apr 2023 at 11:40, Christian Borntraeger
> <borntraeger@linux.ibm.com> wrote:
>> Am 06.04.23 um 11:21 schrieb Peter Maydell:
>>> Christian, does our S390X machine get a guaranteed amount of CPU,
>>> or does it depend on what else is running on the hardware?
>>
>> I think its a shared system with shared CPUs. Can you check the steal
>> time in top or proc? If this is far too high we could ask to give you
>> more weight for that VM.
>
> It's idle at the moment and steal time seems to be low (0.0 .. 0.3);
> I'll try to remember to check next time it's running a job.
>
Do you have /proc/stat ?
next prev parent reply other threads:[~2023-04-06 11:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 15:15 s390 private runner CI job timing out Peter Maydell
2023-04-06 6:57 ` Thomas Huth
2023-04-06 9:21 ` Peter Maydell
2023-04-06 10:40 ` Christian Borntraeger
2023-04-06 10:44 ` Peter Maydell
2023-04-06 11:17 ` Christian Borntraeger [this message]
2023-04-06 12:05 ` Peter Maydell
2023-04-06 12:13 ` Christian Borntraeger
2023-04-06 12:28 ` Peter Maydell
2023-04-06 12:30 ` Thomas Huth
2023-04-06 12:39 ` Peter Maydell
2023-04-06 12:44 ` Christian Borntraeger
2023-04-06 14:18 ` Christian Borntraeger
2023-04-06 12:42 ` Christian Borntraeger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=149e9342-b48b-0871-ee4d-96c6f1d3f198@linux.ibm.com \
--to=borntraeger@linux.ibm.com \
--cc=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).