[racket-dev] Performance regression testing?

From: Jay McCarthy (jay.mccarthy at gmail.com)
Date: Fri Oct 26 11:01:06 EDT 2012

Generally, I look at the DrDr timing graphs and the run-length
overall. The first is good for discrete tests that do benchmarking
(such as tests/racket/benchmarks and tests/racket/stress) or are very
expensive, like the TR tests. The second is good when Matthew does
some VM-level optimization---for example, today DrDr takes about 55
minutes per revision, but it used to be more like 1.15 hours and now
it is testing *more* stuff.


On Fri, Oct 26, 2012 at 7:35 AM, Tony Garnock-Jones <tonyg at ccs.neu.edu> wrote:
> Hi all,
> I have a speculative change to match that I'd like to propose, but before I
> do I'd like to make sure it has no negative performance impact.
> How do people go about checking for performance regressions in core racket
> collections? Is there a standard benchmark suite?
> Regards,
>   Tony
> _________________________
>  Racket Developers list:
>  http://lists.racket-lang.org/dev

Jay McCarthy <jay at cs.byu.edu>
Assistant Professor / Brigham Young University

"The glory of God is Intelligence" - D&C 93

Posted on the dev mailing list.