From: Chet Murthy <chet@watson.ibm.com>
To: Xavier Leroy <xavier.leroy@inria.fr>
Cc: onlyclimb <onlyclimb@163.com>, caml-list@inria.fr
Subject: Re: [Caml-list] speed
Date: Thu, 02 Jan 2003 12:52:25 -0500 [thread overview]
Message-ID: <200301021752.h02HqPXh005051@nautilus-chet.watson.ibm.com> (raw)
In-Reply-To: Your message of "Fri, 03 Jan 2003 14:32:21 +0100." <20030103143221.B29601@pauillac.inria.fr>
Not to contradict Xavier, because in essence, he is right -- Caml is
indeed far faster than Java on any realistic applications in almost
any area I have ever bothered to try -- but the story as to Java is
actually rather complicated.
(1) different JDKs exhibit remarkably different results on real-world
examples, as their implementors have different backgrounds. I
remember that the first JITs all did great on integer and
floating-point loops, and that was _it_ -- the rest of the time, they
were often slower than just a hack like inlining interpreter
code-segments. This is just a human thing.
(2) different JDKs from different manufacturers exhibit different
behaviours. E.g., I find that the Sunsoft JDKs on Solaris are a lot
faster than the Javasoft JDKs on Solaris. I also find (no, I'm not
shilling for IBM) that IBM's JDK on Linux is a lot faster than
Javasoft's. There are, again, social issues involved here, which I am
not sure I am at liberty to discuss.
That said, by and large I find that when you don't go near issues of
allocation and interprocedural optimization, Java is and can be as
fast as Caml. *However*, when you _do_ go near those things, e.g. if
you do anything I/O or string-processing-intensive, well,
go get a rocking chair, 'cos you're gonna have a looong wait.
--chet--
P.S. Or get thee to a caml and get it done. *grin*
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-01-03 14:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 16:00 onlyclimb
2003-01-03 11:38 ` [Caml-list] speed Clemens Hintze
2003-01-03 11:47 ` [Caml-list] speed Noel Welsh
2003-01-02 16:45 ` Chet Murthy
2003-01-03 13:32 ` Xavier Leroy
2003-01-02 17:52 ` Chet Murthy [this message]
2003-01-03 14:53 ` Sven Luther
2003-01-03 15:28 ` Erol Akarsu
2003-01-02 17:53 ` Coyote Gulch test in Caml (was Re: [Caml-list] speed ) Chet Murthy
2003-01-03 15:10 ` Shawn Wagner
2003-01-03 15:56 ` Oleg
2003-01-04 18:31 ` Xavier Leroy
2003-01-18 22:49 ` Oleg
2003-01-18 23:50 ` Shawn Wagner
2003-01-20 21:23 ` David Chase
2003-01-20 21:39 ` Nickolay Semyonov-Kolchin
2003-01-21 0:54 ` Brian Hurt
2003-01-21 13:09 ` David Chase
2003-01-21 13:15 ` Daniel Andor
2003-01-21 20:26 ` Nickolay Semyonov-Kolchin
2003-01-19 10:33 ` Siegfried Gonzi
2003-01-19 10:34 ` Siegfried Gonzi
2003-01-21 9:56 ` [Caml-list] Re: Coyote Gulch test in Caml Xavier Leroy
2003-01-21 15:57 ` Brian Hurt
2003-01-27 16:58 ` Daniel Andor
2003-01-28 8:27 ` Christian Lindig
2003-01-05 1:13 ` [Caml-list] speed Brian Hurt
2003-01-05 1:48 ` Michael Vanier
2003-01-07 16:03 isaac gouy
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=200301021752.h02HqPXh005051@nautilus-chet.watson.ibm.com \
--to=chet@watson.ibm.com \
--cc=caml-list@inria.fr \
--cc=onlyclimb@163.com \
--cc=xavier.leroy@inria.fr \
/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