This is the mail archive of the
mailing list for the Mauve project.
- To: mauve <firstname.lastname@example.org>
- Subject: Benchmarks
- From: Artur Biesiadowski <email@example.com>
- Date: Thu, 11 Feb 1999 15:26:29 +0100
I wonder if it would be right to include benchmarks inside mauve.
Mauve is designed to help in testing core lib. But in addition to just
passing JCK, I think that implementors might be interested how given
change will change speed of given class. Of course they can write small
test classes (I have done really a lot of them during tya testing).
Maybe such things can find their place inside mauve ?
I'm thinking about creating additional class type and additional tag
(benchmark). Or maybe instead of tag, we can just hardcode that class
named benchmark.java in given directory performs benchmarks. Then user
could just run something like
make 'TAGS=!java java.util.Vector' benchmark
and check results.
Details of how it should be performed - by time command, measuring
milliseconds from java program are secondary problem.