On Wed, Sep 05, 2001 at 10:24:05AM -0500, Christian T. Steigies wrote: > But this time I registered it with wanna-build, if you want to build it > yourself, just register it and its yours. No, given that it takes me 2 days to build it, I think it's probably just as well if the autobuilders handle it. > > dpkg-buildpackage: binary only upload (no source included) > > Command being timed: "dpkg-buildpackage -uc -B" > > User time (seconds): 122976.66 > > System time (seconds): 19898.74 > > Percent of CPU this job got: 8% > > Elapsed (wall clock) time (h:mm:ss or m:ss): 46:10:09 > Ouch. Does that mean 8% of 46h is the time you actually needed for the > build? Or NBD took 8% out of that for its own purposes? I didn't use NBD for this build; as I said, I couldn't get NBD to work. No, the low CPU utilization means that the box spent most of its time doing things other than compiling code. On most architectures an X build consumes upwards of 95% CPU if I don't have the machine doing something else. The low figure above is, I fear, a symptom of the completely crappy disk I/O. I could be wrong, though, and I'd love it if someone with more of a clue enlightened me. > cts@aahz:~/logs>avg-pkg-build-time xfree86 > xfree86: 26:04:38 (6 entries, sigma 05:46:35) > cts@aahz:~/logs>avg-pkg-build-time -s xfree86 > xfree86: 931808k (1122525k lastest) > > Now did the debug patch give you any insight as to where we have to start > fixing? I haven't looked into it yet. -- G. Branden Robinson | If a man ate a pound of pasta and a Debian GNU/Linux | pound of antipasto, would they branden@debian.org | cancel out, leaving him still http://people.debian.org/~branden/ | hungry? -- Scott Adams
Attachment:
pgpWE9ulv6SSf.pgp
Description: PGP signature