Browse thread
Is OCaml fast?
-
Thanassis Tsiodras
- Gregory Bellier
- Sylvain Le Gall
- Dario Teixeira
- Gerd Stolpmann
- Fabrice Le Fessant
- Oliver Bandel
- Isaac Gouy
- David Allsopp
- Cedric Cellier
- Vincent Aravantinos
- Isaac Gouy
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: | 2010-11-23 (17:53) |
From: | Isaac Gouy <igouy2@y...> |
Subject: | Re: Is OCaml fast? |
Christophe TROESTLER <Christophe.Troestler+ocaml <at> umh.ac.be> writes: > > On Tue, 23 Nov 2010 02:03:48 +0000, Isaac Gouy wrote: > > > > > C version : 12.11 secs > > > OCaml version : 47.22 secs > > > OCaml version with GC parameters tuned ("interesting alternative" > > section) : 12.67 secs > > > > And of course you know because that GC tuned OCaml program is shown > > on the > > benchmarks game website > > http://shootout.alioth.debian.org/u32/program.php?test=binarytrees& > > lang=ocaml&id=1 > > Since you are here, please explain why C can use memory pools and vec > tor instructions but tuning the GC of OCaml ― although it is part of > the standard library ― is considered an “alternativeâ€. You seem to be suggesting that "tuning the GC" is considered "alternative" only for OCaml programs. You seem to be suggesting that "tuning the GC" is considered "alternative" for every task. Neither is true. You seem to be suggesting some kind of equivalence between vector instructions and "tuning the GC". You haven't said why they should be considered equivalent. Nor have you said why you think C should not be allowed to use memory pools.