From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, sean.brogan@microsoft.com,
Bret Barkelew <bret.barkelew@microsoft.com>
Subject: Re: [edk2-devel] [EXTERNAL] [edk2-devel] Information about the VMs used to do EDK2 CI?
Date: Sat, 21 Mar 2020 17:03:09 -0600 [thread overview]
Message-ID: <f93995bb-479f-ce24-efa8-465a8dcb63b9@bsdio.com> (raw)
In-Reply-To: <4287.1584808895303845810@groups.io>
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
Thank you. I think we probably do want to detect the number of threads
available: I'll see if I can work on that.
I'll plan to set up my own Azure self-hosted agent for doing more
extensive testing for FreeBSD and Bhyve.
--
Rebecca Cran
On 3/21/20 10:41 AM, Sean via Groups.Io wrote:
> Rebecca - I think for any platform testing it would make more sense to
> use self hosted agents. They could even be your own VM. QEMU and
> emulator might be the two where we could explore using the DevOps VMs
> but I worry we will spend too much time downloading and install
> dependencies since the VM is clean on each run.
>
> We can detect the number of threads available and call make with the
> associated parameters. That might help speed it up and would be safe
> to use.
>
> The doc says they are DS2v2 instances which have the following.
>
> TABLE 2 Size vCPU Memory: GiB Temp storage (SSD) GiB Max data
> disks Max cached and temp storage throughput: IOPS/MBps (cache size
> in GiB) Max uncached disk throughput: IOPS/MBps Max NICs/Expected
> network bandwidth (Mbps)
>
> Standard_DS2_v2 2 7 14 8 8000/64 (86) 6400/96 2/1500
>
>
[-- Attachment #2: Type: text/html, Size: 8418 bytes --]
next prev parent reply other threads:[~2020-03-21 23:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 1:33 Information about the VMs used to do EDK2 CI? Rebecca Cran
2020-03-21 1:46 ` [EXTERNAL] [edk2-devel] " Bret Barkelew
2020-03-21 3:15 ` Rebecca Cran
2020-03-21 16:41 ` [edk2-devel] " Sean
2020-03-21 23:03 ` Rebecca Cran [this message]
2020-03-23 12:38 ` Laszlo Ersek
2020-03-28 20:23 ` Sean
2020-03-28 21:41 ` Andrew Fish
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-list 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=f93995bb-479f-ce24-efa8-465a8dcb63b9@bsdio.com \
--to=devel@edk2.groups.io \
/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