35 ms·

It took 2 hours on a pristine 48-core Azure VM from start to finish; wrote some details here when I was playing with it: https://github.com/ungoogled-software/u

It took 2 hours on a pristine 48-core Azure VM from start to finish; wrote some details here when I was playing with it: https://github.com/ungoogled-software/ungoogled-chromium-windows/issues/102 https://github.com/ungoogled-software/ungoogled-chromium-win... It's likely it'll be faster if I build on bare-metal on my box; spun up a VM because the build does all kinds of stuff (downloads binaries, spits up temporaries all over the place, etc.).

gruez 5y ago
>pristine 48-core Azure VM 1. it's actually 24 physical cores, since azure counts hyperthreads as "vCPUs". still, that still seems slow compared to my own build times. 2. azure VMs have horrendous IO on the persistent data drives. You can probably get a small to medium speed improvement by moving your build to the D: drive.
- heavyset_go 5y ago
  > 2. azure VMs have horrendous IO on the persistent data drives. This. If you want to benchmark builds on Azure, building on a tmpfs or ramfs will help mitigate disk IO latency, although tmpfs might swap.