From: Jon Harrop <jon@jdh30.plus.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Memory allocation nano-benchmark.
Date: Tue, 15 Feb 2005 20:51:54 +0000 [thread overview]
Message-ID: <200502152051.55292.jon@jdh30.plus.com> (raw)
In-Reply-To: <000c01c51369$278441c0$0100a8c0@mshome.net>
On Tuesday 15 February 2005 14:17, Frédéric Gava wrote:
> stupid question, do you use the "-unsafe" option of ocamlopt. It is better
> for arrays...
Having seen a physics student write a C++ program which invalidly read from
a[n], resulting in him drawing scientific conclusions from physically-
realistic but non-deterministically- and unquantifiably-erroneous results, I
strongly advise people to take the extra ~10% performance hit and use array
bounds checking all the time.
Indeed, I'm in the "remove -unsafe" camp. Even if OCaml only hoisted bounds
checks in the simplest of cases, I think there would be a strong case for
removing this option.
> > The code using ordinary arrays runs in 2.8 seconds,
> > using bigarray 0.7 seconds. 4 x 0.7 = 2.8.
> >
> > bigarray is 4 times faster to write than three level
> > ordinary array.
The current array implementation is not great for large array-based
computations but I'm not sure that this is such a failing because I don't
think people should be coding large array-based computations in OCaml. Either
use a dedicated numerical library for handling large matrices/tensors or use
a more appropriate data structure (typically a tree) to solve "the bigger"
problem. The asymptotic complexity of such array based computations is rarely
good and, consequently, real-time performance is often unnecessarily poor.
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
next prev parent reply other threads:[~2005-02-15 20:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 15:15 Christian Szegedy
2005-02-10 14:47 ` [Caml-list] " Frédéric Gava
2005-02-10 15:19 ` skaller
2005-02-10 16:36 ` Frédéric Gava
2005-02-10 17:56 ` Frédéric Gava
2005-02-10 19:56 ` Christian Szegedy
2005-02-10 23:58 ` Frédéric Gava
2005-02-11 9:22 ` Frédéric Gava
2005-02-11 13:04 ` skaller
2005-02-11 13:33 ` skaller
2005-02-11 21:07 ` Oliver Bandel
2005-02-12 0:44 ` skaller
2005-02-15 14:17 ` Frédéric Gava
2005-02-15 19:19 ` Christian Szegedy
2005-02-15 20:51 ` Jon Harrop [this message]
2005-02-16 8:19 ` Ville-Pertti Keinonen
2005-02-16 9:54 ` Jon Harrop
2005-02-16 10:56 ` Ville-Pertti Keinonen
2005-02-11 0:55 ` skaller
2005-02-10 14:56 ` Jon Harrop
2005-02-10 15:32 ` Ville-Pertti Keinonen
2005-02-10 14:59 ` John Prevost
2005-02-10 16:50 ` Marwan Burelle
2005-02-10 19:20 ` Christian Szegedy
2005-02-10 19:40 ` Jon Harrop
2005-02-11 11:26 ` Oliver Bandel
2005-02-12 13:42 ` Christian Szegedy
2005-02-11 1:04 ` skaller
2005-02-11 11:28 ` Oliver Bandel
2005-02-12 0:01 ` Guillaume
2005-02-12 0:36 ` skaller
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=200502152051.55292.jon@jdh30.plus.com \
--to=jon@jdh30.plus.com \
--cc=caml-list@yquem.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