From: Cedric Berger <cedric@wireless-networks.com>
To: green@cygnus.com
Cc: rhug-rhats@sources.redhat.com, java@gcc.gnu.org
Subject: Re: Xalan: gcj -vs- jre 1.3
Date: Sat, 15 Sep 2001 14:13:00 -0000 [thread overview]
Message-ID: <3BA3C775.8070705@wireless-networks.com> (raw)
In-Reply-To: <200109152041.NAA22016@fencer.cygnus.com>
Anthony Green wrote:
>Transform of rhug.rml via rhug-info.xsl took 219 ms
>
Do you understand, I hope, that this only measures the startup time
of the VM. This is where GCJ shines and where GCJ will be very useful.
Of course, nobody in is right mind will invoke the following command
to transform XSL documents in a production environment.
java org.apache.xalan.xslt.Process -IN rhug.rml -XSL rhug-info.xsl -OUT index.html -DIAG
What would be interresting is to "daemonize" the process, and see
how long it takes to transform a single document with a *running* VM.
And also, of course, since you used the latest GCJ, would you care
to do the same test with the latest JRE, which is 1.3.1_01 if I'm not
mistaken?
Cedric
next prev parent reply other threads:[~2001-09-15 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-15 13:41 Anthony Green
2001-09-15 14:13 ` Cedric Berger [this message]
2001-09-15 15:22 ` Anthony Green
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=3BA3C775.8070705@wireless-networks.com \
--to=cedric@wireless-networks.com \
--cc=green@cygnus.com \
--cc=java@gcc.gnu.org \
--cc=rhug-rhats@sources.redhat.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).