From: Xavier Leroy <xavier.leroy@inria.fr>
To: briand@aracnet.com
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] interesting array efficiency observations
Date: Sun, 9 May 2004 10:24:24 +0200 [thread overview]
Message-ID: <20040509102424.A22305@pauillac.inria.fr> (raw)
In-Reply-To: <16541.9013.181806.9426@soggy.deldotd.com>; from briand@aracnet.com on Sat, May 08, 2004 at 11:13:09AM -0700
> I was investigating the use of 1-D bigarray's vs Array and noticed
> that the 1-D bigarray using c_layout seems to be slower than Array.
> Is this an expected result ?
Yes. When compiling to bytecode (or at the top-level), all bigarray
accesses go through a generic access function that is polymorphic over
the number of dimensions, the array type and the array layout, and is
therefore somewhat expensive.
When compiling to native code, efficient inline code is generated
instead for accesses to 1, 2 and 3-dimensional arrays, provided the
full type of the bigarray (including layout and element type) is known.
In this case, the inline access code is almost as efficient as that
for accessing a regular array: just one extra indirection.
- Xavier Leroy
-------------------
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:[~2004-05-09 8:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-08 18:13 briand
2004-05-08 21:21 ` Yamagata Yoriyuki
2004-05-08 22:45 ` Olivier Grisel
2004-05-09 0:25 ` Christophe TROESTLER
2004-05-09 0:48 ` Yamagata Yoriyuki
2004-05-09 8:24 ` Xavier Leroy [this message]
2004-05-09 14:07 ` malc
2004-05-11 5:04 ` briand
2004-05-12 15:30 ` Christophe TROESTLER
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=20040509102424.A22305@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=briand@aracnet.com \
--cc=caml-list@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;
as well as URLs for NNTP newsgroup(s).