Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Sebastien Furic <sebastien.furic@tni-valiosys.com>
To: Pierre Weis <pierre.weis@inria.fr>
Cc: frisch@clipper.ens.fr, caml-list@inria.fr
Subject: Re: [Caml-list] Num library
Date: Fri, 11 Oct 2002 11:26:49 +0200	[thread overview]
Message-ID: <3DA69959.1E2480BB@tni-valiosys.com> (raw)
In-Reply-To: <200210101708.TAA06448@pauillac.inria.fr>

Pierre Weis wrote:
> 
> >  I made some benchmarks with Dolphin Smalltalk (a pure Smalltalk
> > bytecode interpreter) and O'Caml (using ocamlopt) a few months ago. To
> > my great surprise, Dolphin Samlltalk outperformed O'Caml by a factor of
> > 4 over various tests IIRC. I think the same results may be obtained with
> > other modern big numbers implementations against O'Caml's one.
> [...]
> 
> What do you know about Caml big numbers library ? Are you sure to have
> used the proper layer of the library tuned to performance or have you
> used the casual layer tuned to coding facility ?
> 
> What do you know of the Smalltalk big numbers library ? In which
> language is it written ? What are the algorithms used ?
> 
> What were your benchmark programs ? What are your figures ?
> 
> Be serious on such a topic please! Comparing arithmetic packages is
> not a trivial task and you cannot state ``Dolphin Samlltalk
> outperformed O'Caml by a factor of 4'' without strong arguments and
> evidence that this is indeed true.
> 
> Pierre Weis

 My intention was not to begin a flame war.

 Dolphin's numerical algorithms are written in assembly language, like
all time-critical parts of the interpreter. Unfortunately, Dolphin's
team just announced "new faster algorithms" (and didn't give information
about the algorithms they use).
 Of course, I tried to tune my O'Caml code but I couldn't beat Dolphin's
implementation (despite the use of Nat etc.). Dolphin's bignums are
natively supported by the language and there is no way to hack them.
This is however very convenient for occasional users like me because I
don't have many time to "hack" numerical packages.
 Please note that I'm perfectly happy with O'Caml though.

 Regards,
 Sebastien.
-------------------
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:[~2002-10-11  9:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-10  8:42 Alain Frisch
2002-10-10  9:42 ` sebastien FURIC
2002-10-10 14:56   ` Yaron M. Minsky
2002-10-10 17:14     ` Pierre Weis
2002-10-10 18:53       ` Alain Frisch
2002-10-11 20:01         ` Pierre Weis
2002-10-10 19:45       ` Yaron M. Minsky
2002-10-10 17:08   ` Pierre Weis
2002-10-11  9:26     ` Sebastien Furic [this message]
2002-10-11 20:17       ` Pierre Weis
2002-10-11 10:22     ` Alessandro Baretta
2002-10-11 13:23 ` Claude Marche
2002-10-11 16:14   ` Sebastien Furic
2002-10-11 14:08 ` Jean-Christophe Filliatre
2002-10-11 18:35   ` "custom" operators in caml (was: Re: [Caml-list] Num library) Chris Hecker
2002-10-11 20:30   ` [Caml-list] Num library Pierre Weis

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=3DA69959.1E2480BB@tni-valiosys.com \
    --to=sebastien.furic@tni-valiosys.com \
    --cc=caml-list@inria.fr \
    --cc=frisch@clipper.ens.fr \
    --cc=pierre.weis@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