532979 - Time builds on new 1U hardware

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[John Ford [:jhford] CET/CEST Berlin Time]

Before we set everything up for a buildslave, we should first do some sanity check timings on the 1U boxes and VMs.  I have written a script which can be used to do some timing checks.  There are a bunch of global variables at the top of the script which can be changed, as well as the logic in the main loop

See bug 532976 for scripts that are to be run

Comment 1

[John Ford [:jhford] CET/CEST Berlin Time]

using bm-win32-test01.build

Comment 2

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

Just met with mrz, jhford. New, different, 1U hardware is in transit, which should support exiting Win2003 toolchain. 

Moving to Future until the newer hardware arrives.

Comment 3

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

Moving from Future as the hardware is supposedly now online.

jhford did timing work on linux-1u box earlier, so pushing this win32-1u box timing work to him.

Comment 4

[John Ford [:jhford] CET/CEST Berlin Time]

Timing seem to point towards using hardware instead of vms.

Windows Clobber PGO builds are 71 minutes instead of  3.5-4.5 hours, Plain clobber are 28.

Linux Clobber builds are 13 minutes instead 58 minutes.