Hi Stefan, On Mon, Oct 1, 2012 at 9:14 AM, Stefan Behnel <stefan...@behnel.de> wrote: > Either it benchmarks mostly a specific part of the overall runtime, in that > case, there's no reason for it to take ages. It can just be stripped down > to run a reasonably sized workload that exercises the target code well. > > If it does not benchmark anything specific, and thus cannot be sized down > in any way, then what's the interesting thing that its broad and unspecific > result would tell us?
Broad and unspecific results are what is most interesting from the point of view of the end user using a large program. For example, changes to the cycle collector of CPython, as occurred between 2.6 and 2.7, had good results on large and complicated programs but I guess not on anything typically benchmarkish. As a result, at least one "large and complicated" program runs quite a lot faster on CPython. This large program is included into our benchmark suite. Feel free to throw it away on first principles, but we would disagree with your approach. A bientôt, Armin. _______________________________________________ Speed mailing list Speed@python.org http://mail.python.org/mailman/listinfo/speed
