On Fri, Oct 17, 2014 at 02:19:29PM +0100, Dave Mitchell wrote: > > > I want to discuss some modest proposals for better testing of performance > > > and optimisations. The first four suggestions are simple, concrete, and (I > > > hope) non-controversial. The fifth is more woolly and up for discussion. I've now pushed the branch smoke-me/davem/perf, which does the following: create t/perf/ create t/perf/opcount.t with a single example test rename t/op/opt.t -> t/perf/optree.t create t/perf/speed.t with a single example test create t/perf/benchmarks with a simple sample benchmark snippet create t/perf/benchmarks.t that tests the basic syntax of t/perf/benchmarks I have not yet done (and don't intend to do immediately): create t/perf/peek.t or similar, to examine SV fields create tools to run timings and cachegrinds of t/perf/benchmarks code snippets, possibly across multiple perls create a test file that examines perl -Dfoo debugging output -- A major Starfleet emergency breaks out near the Enterprise, but fortunately some other ships in the area are able to deal with it to everyone's satisfaction. -- Things That Never Happen in "Star Trek" #13Thread Previous | Thread Next