Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 31 Aug 2003 17:15:21 -0500
From:      "Charles Howse" <chowse@charter.net>
To:        "'Kent Stewart'" <kstewart@owt.com>, "'ODHIAMBO Washington'" <wash@wananchi.com>
Cc:        freebsd-questions@freebsd.org
Subject:   RE: scripting the buildworld/installworld process
Message-ID:  <002701c3700d$5ef73190$04fea8c0@moe>
In-Reply-To: <200308311500.29938.kstewart@owt.com>

next in thread | previous in thread | raw e-mail | index | archive | help
> When I started timing my buildworlds, I figured out that you need=20
> everything but the right hand stuff in the following
>=20
> AMD Athlon 2000+ XP
> 877.636u 233.835s 23:02.33 80.4%        1350+1662k 46008+7469io=20
> 2359pf+0w
> bw w -j2
> 891.151u 303.327s 35:02.77 56.8%        1305+1600k 52256+138679io=20
> 2749pf+0w
> bw w -j3
> 894.429u 305.373s 31:29.87 63.4%        1305+1595k 50306+138970io=20
> 1914pf+0w
> bw w -j4
> 893.259u 310.180s 32:43.57 61.2%        1308+1597k 56102+138705io=20
> 2145pf+0w
> bw w -j5
> 893.563u 311.353s 30:31.44 65.7%        1302+1591k 53927+138930io=20
> 2331pf+0w
>=20
> The wall clock time is really how efficient your process is. The fact=20
> that your user time or sys time is faster doesn't mean much=20
> if the wall=20
> clock time is 1/3 longer.=20
>=20
> I haven't automated timing this part because I time the whole=20
> script and=20
> not just the build. I would cut off the right hand side but it is too=20
> trivial to use just "time mkworld" and cut and paste the time into a=20
> "cat >> times.log" of my builds. This also lets me add comments in=20
> addition to the build time information. For example, the AMD=20
> 2000+ was=20
> important because that was the first build after an upgrade from an=20
> Intel P III 866. The upgrade was needed because the old mobo went=20
> flaky.
>=20
> I think that once you have it setup, I will probably make my=20
> KISS simple=20
> script more complicated :). I have one machine that the mouse doesn't=20
> work in single user mode and including the timing into my mkworld=20
> script would save time. I can always go back and edit my time log to=20
> include the comments. If I have a choice, I would add the=20
> date field to=20
> the right hand side so that I can connect the time to the build log.

I read "briefly" your web page about the -j urban legend.
>From the stats above, it looks like it runs faster without the -j
flag...?
That might be something interesting to play with on my Celeron 300 w/
64MB.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002701c3700d$5ef73190$04fea8c0>