On Thu, Feb 20, 2014 at 03:27:10PM -0500, Karl Nordstrom wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > How much time does it take to "smoke test" Perl?
We don't know. It really depends on the hardware. I don't think anyone has a good idea how z/OS hardware performance compares with Linux or Unix systems. In that, on a current 24 core x86_64 server I can do a complete clean build and test of perl in under 5 minutes, with parallel make and parallel tests. The 48 core AIX machine in the GCC compiler farm is pretty fast too. But on the PA-RISC HP/UX machine that Merijn has made available, it takes a bit than an hour, and I think that an ever older machine that he had was taking about 6 hours per build. A Raspberry Pi can build and test in 4 or 5 hours (it's probably limited by the SD card, not the CPU) Ideally a "smoke test" is (minimum) a matrix of 4 builds of perl (optimisation DEBUGGING, no optimisation) x (unthreaded threaded) so that machine of Merijn's was taking most of 24 hours to do a run. Nicholas Clark
