Thanks! It was the singe-threaded part that I was interested in. But also, it sounds like for more complex/in-depth testing such as running QEMU to do runtime validation and regression-testing of OVMF etc. we'll want to set up our own agents, since the hosted ones are relatively restrictive. -- Rebecca Cran On 2020-03-20 19:46, Bret Barkelew wrote: > > CI runs on the DevOps pool for ubuntu-latest and windows-latest, > respectively… > > https://github.com/tianocore/edk2/blob/0c8ea9fe1adbbee230ee0c68f28b68ca2b0534bc/.azurepipelines/Ubuntu-GCC5.yml#L16 > > https://github.com/tianocore/edk2/blob/0c8ea9fe1adbbee230ee0c68f28b68ca2b0534bc/.azurepipelines/Windows-VS2019.yml#L17 > >   > > As for OS, it looks like this table is kept up-to-date: > > https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops#use-a-microsoft-hosted-agent > >   > > I **think** they may be assumed to be single-threaded and parallelism > is accomplished via “jobs”: > > https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops#capabilities-and-limitations > > (@Sean may correct me on that) > >   > > What details do you need and I’ll try to find them. 😊 > >   > > - Bret > >   > > *From: *Rebecca Cran via Groups.Io > *Sent: *Friday, March 20, 2020 6:33 PM > *To: *devel@edk2.groups.io > *Subject: *[EXTERNAL] [edk2-devel] Information about the VMs used to > do EDK2 CI? > >   > > I was wondering if it might be possible to get information about the VMs > used to run EDK2 CI? > > For example I noticed the Edk2ToolsBuild.py script doesn't try and build > BaseTools in parallel, causing it to take 45 seconds - whereas it takes > around 10 when run with "make -j4" and 6 with "make -j16". However, > without knowing the specifications of the VMs used, I'm not sure if I > should work on optimizing things like that to run better. > > > -- > Rebecca Cran > > > > > >   >