public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Artur Biesiadowski <abies@pg.gda.pl>
To: mauve <mauve-discuss@sourceware.cygnus.com>
Subject: Benchmarks
Date: Thu, 11 Feb 1999 06:59:00 -0000	[thread overview]
Message-ID: <36C2E895.B060177B@pg.gda.pl> (raw)

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.

Artur


WARNING: multiple messages have this Message-ID
From: Artur Biesiadowski <abies@pg.gda.pl>
To: mauve <mauve-discuss@sourceware.cygnus.com>
Subject: Benchmarks
Date: Thu, 01 Apr 1999 00:00:00 -0000	[thread overview]
Message-ID: <36C2E895.B060177B@pg.gda.pl> (raw)
Message-ID: <19990401000000.-RUm6qbZ-Y71JCjGBRYSxd3HBQRIPyTzKL1QR4FQ3oI@z> (raw)

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.

Artur



             reply	other threads:[~1999-02-11  6:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-11  6:59 Artur Biesiadowski [this message]
1999-04-01  0:00 ` Benchmarks Artur Biesiadowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=36C2E895.B060177B@pg.gda.pl \
    --to=abies@pg.gda.pl \
    --cc=mauve-discuss@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).