Date: Fri, 5 Nov 2010 13:26:07 +0100 From: Erik Cederstrand <erik@cederstrand.dk> To: grarpamp <grarpamp@gmail.com> Cc: freebsd-performance@freebsd.org Subject: Re: Tracking performance areas over time Message-ID: <291C14E3-1BEF-4C1E-8BCD-BF8FB3BCE6EB@cederstrand.dk> In-Reply-To: <AANLkTim6N=rRS6ZwofnyXBud969QhHjB9Mk0jLuH%2BMdt@mail.gmail.com> References: <AANLkTim6N=rRS6ZwofnyXBud969QhHjB9Mk0jLuH%2BMdt@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail-1335--732361135 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Den 04/11/2010 kl. 18.07 skrev grarpamp: > Not as comparison with FreeBSD but ideas for > tracking FreeBSD performance across release/releng. >=20 > = http://www.phoronix.com/scan.php?page=3Darticle&item=3Dlinux_2612_2637&num= =3D1 >=20 > Provided the version of the unit test is kept the > same and it compiles across all FreeBSD release/releng > since 2.x, automating like this shouldn't be hard. >=20 > Natively release install [or selfhost build releng > on top], and archive the base platforms once. Copy > over to a test disk and reboot it natively on > demand, insert each unit test module as desired, > record data, copy disk and boot next version, etc... I actually developed something like this for FreeBSD two years ago. = Included were build scripts for producing releases, a description of = setting up netbooting slaves, a small collection of benchmarks, a = database and a web interface. In lack of hardware and time on my part to = run the tests, it never got off the ground. Apart from an update to run = on SVN instead of CVS, it should be functional. If anyone's interested, please contact me. Thanks, Erik= --Apple-Mail-1335--732361135--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?291C14E3-1BEF-4C1E-8BCD-BF8FB3BCE6EB>