Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 31 Jan 2005 15:24:39 +0000 (GMT)
From:      Robert Watson <rwatson@FreeBSD.org>
To:        "Jim C. Nasby" <decibel@decibel.org>
Cc:        freebsd-performance@freebsd.org
Subject:   Re: Automated performance testing
Message-ID:  <Pine.NEB.3.96L.1050131152227.35704J-100000@fledge.watson.org>
In-Reply-To: <20050130230527.GR64304@decibel.org>

next in thread | previous in thread | raw e-mail | index | archive | help

On Sun, 30 Jan 2005, Jim C. Nasby wrote:

> With all the discussion of performance testing between 4.11, 5.3, and
> Linux, would it be useful to make performance testing part of the
> automated testing that already occurs (via tinderbox, iirc). Doing so
> might make it easier to detect performance impacting changes, as well as
> making performance testing easier in general. 

Yes, it would be quite valuable.  I've been hoping to set up something
like this for a while, but have never found the opportunity.  I have been
tracking the long term behavior of MySQL performance as part of the
netperf work, but because testing is fairly hardware and time consuming,
the polling intervals are uneven, and not quite close enough to nail down
culprits.  I'd really like to see a small and fairly well-defined set of
tests run every couple of days so we can show long term graphs, and catch
regressions quickly.  Unfortunately, this is a bit harder than
tinder-boxing, because it involves swapping out whole system
configurations, recovering from the inevitable failure modes, etc, which
proves to be the usual sticking point in implementing this.  However, I'd
love to see someone work on it :-).

Robert N M Watson




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1050131152227.35704J-100000>