caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Gregory Morrisett" <jgm@CS.Cornell.EDU>
To: "Chet Murthy" <chet@watson.ibm.com>,
	"Lex Stein" <stein@eecs.harvard.edu>
Cc: "Ocaml Mailing List" <caml-list@inria.fr>
Subject: RE: [Caml-list] comparison with C performance
Date: Fri, 2 May 2003 02:02:41 -0400	[thread overview]
Message-ID: <FB4F95390166B14C90E4DD950D69D6E246F2DB@EXCHVS2.cs.cornell.edu> (raw)

>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.

Erm, no.  The protocol optimizations used in Ensemble were
never translated back into C.  He compared against an older
version (Horus) which used different algorithms and 
acknowledged that if you translated the ideas from Ensemble
back into C, you'd probably get a performance win.  They
never bothered to do this because the Caml code had
acceptable performance.

The key thing is that it was too hard to do the restructuring
needed to experiment with new approaches to the group
communications protocol in C.  By coding in Caml, he
was able to make massive rearrangements until he got
the right algorithm.

So, the point is that (a) algorithms matter a lot more
than the delta between Caml vs. C, (b) it's easier to 
experiment with better algorithms in a higher-level language.

-Greg

-------------------
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


             reply	other threads:[~2003-05-02  6:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-02  6:02 Gregory Morrisett [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
2003-05-01 19:08       ` Brian Hurt
2003-05-01 19:13   ` Eray Ozkural

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=FB4F95390166B14C90E4DD950D69D6E246F2DB@EXCHVS2.cs.cornell.edu \
    --to=jgm@cs.cornell.edu \
    --cc=caml-list@inria.fr \
    --cc=chet@watson.ibm.com \
    --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).