From: Chet Murthy <chet@watson.ibm.com>
To: Lex Stein <stein@eecs.harvard.edu>
Cc: Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] comparison with C performance
Date: Sun, 27 Apr 2003 15:04:07 -0400 [thread overview]
Message-ID: <200304271904.h3RJ47xM007576@nautilus-chet.watson.ibm.com> (raw)
In-Reply-To: Your message of "Thu, 01 May 2003 14:38:24 EDT." <Pine.BSF.4.51.0305011437350.75493@bowser.eecs.harvard.edu>
Hmmm .. Lex, are you aware of Ensemble?
Mark Hayden basically proved that if you properly manage memory and a
few other things, well, you can be faster than C, unless the C program
is (ahem) trivial.
some more details: Mark showed that for a rather complicated network
protocol stack, a CAML implementation was a *lot* faster than a
highly-optimized C implementation.
The key things he was able to do were:
(a) since its in ML, you can be a lot more aggressive about
optimization
(b) effective memory-management of buffers in ML -- don't just leave
it to the GC
(c) serious reliance on the inliner
There were a few other things, but this is a good start.
Cheers,
--chet--
-------------------
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-05-02 4:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-01 15:27 [Caml-list] OT: Java Performance Brian Hurt
2003-05-01 17:29 ` [Caml-list] comparison with C performance Lex Stein
2003-05-01 17:55 ` Miles Egan
2003-05-01 18:24 ` Lex Stein
2003-05-01 18:48 ` Miles Egan
2003-05-01 18:38 ` Lex Stein
2003-04-27 19:04 ` Chet Murthy [this message]
2003-05-01 19:08 ` Brian Hurt
2003-05-01 19:13 ` Eray Ozkural
2003-05-02 6:02 Gregory Morrisett
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=200304271904.h3RJ47xM007576@nautilus-chet.watson.ibm.com \
--to=chet@watson.ibm.com \
--cc=caml-list@inria.fr \
--cc=stein@eecs.harvard.edu \
/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 NNTP newsgroup(s).