James E Keenan wrote:
What I would like to have is a benchmark test I could run which, on the one hand, gives a small resource machine a good workout, but, on the other hand, is small enough for me to run it consecutively enough times to give me a statistically significant result in testing the various garbage-collection-focused branches. For example, I know that regardless of which machine I test on, t/compilers/opsc/02-parse-all-ops.t takes longer than just about any file in our test suite. If I were able to run it 30 times on master and 30 times in a GC-branch, I would have a good measure of the degree to which a GC-branch improves over master (if indeed it does improve over master ;-) ). The problem is that 02-parse-all-ops.t takes so long to run on small-resource machines that I can not, in practical terms, afford to run it 30 times in a row. What I'd like is a test that takes say, about 4 seconds to run on a small resource box (and, of course, much faster on most contemporary machines) so that I could run it 30 times in two minutes on a given branch. That way, I could relatively quickly compare various branches.
I never got any response to this post last year. The need is still there: I've been asked to test the compreg_imcc branch on both of my machines. Can anyone help?
Thank you very much. kid51 _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
