From: Yotam Barnoy <yotambarnoy@gmail.com>
To: Markus Mottl <markus.mottl@gmail.com>
Cc: Damien Guichard <alphablock@orange.fr>,
Caml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] How much optimized is the 'a option type ?
Date: Fri, 17 Jan 2014 10:49:50 -0500 [thread overview]
Message-ID: <CAN6ygO=USdGy8LguaMdK-fL30bomgQiuUaYSEewdF=tohXcgkw@mail.gmail.com> (raw)
In-Reply-To: <CAP_800qH1ZYj1gy7_xw3OOpR_As5wtJZTy80JpJZANCWaZaKOw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2573 bytes --]
That reminds me -- what is the situation regarding inlining? Is there work
being done on inlining from other modules? Is heavy inlining being done
within a module? Would it be possible to annotate with [@@inline] to give
hints to the compiler at some point?
-Yotam
On Fri, Jan 17, 2014 at 9:36 AM, Markus Mottl <markus.mottl@gmail.com>wrote:
> Others have already answered about memory representation, but there is
> one thing about allocations that many OCaml programmers may not yet be
> aware of and that can make a noticeable performance difference when
> used wisely: the OCaml compiler will inspect your code and, under the
> right conditions, batch together allocations. E.g. consider this
> function (references are records, btw.):
>
> let f n =
> let x = ref (ref (Some (Some n))) in
> [(x, n); (x, n)]
>
> One might naively assume that this would lead to seven or so
> allocations. But if you inspect the assembly, you'll see only one
> allocation followed by mere initialization assignments.
>
> Such allocation batches can break if, for example, the code calls
> non-inlined (e.g. recursive or external) functions. I'm not quite
> sure about all the rules there, but it's generally trivial to just
> look at the assembler output to find out what the compiler is doing.
> In some cases merely calling all functions before any allocations take
> place can speed up your code. There are even cases where it may be
> more efficient to allocate several values in one chunk though only
> some may be needed depending on branches taken later.
>
> Regards,
> Markus
>
> On Fri, Jan 17, 2014 at 2:35 AM, Damien Guichard <alphablock@orange.fr>
> wrote:
> > Hello,
> >
> > Compared to the code :
> >
> > type 'a option = None | Some of 'a
> >
> > How do an 'a option value performs ?
> > Any allocation saved ?
> > Any indirection removed ?
> >
> > Is 'a option just like any sum type ?
> > Or is 'a option more like an ANSI C pointer type ?
> >
> > Regards,
> >
> > Damien Guichard
> >
> >
> >
> > --
> > Caml-list mailing list. Subscription management and archives:
> > https://sympa.inria.fr/sympa/arc/caml-list
> > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> > Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>
>
> --
> Markus Mottl http://www.ocaml.info markus.mottl@gmail.com
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
[-- Attachment #2: Type: text/html, Size: 3934 bytes --]
next prev parent reply other threads:[~2014-01-17 15:50 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 7:35 Damien Guichard
2014-01-17 7:55 ` David House
2014-01-17 8:16 ` Julien Blond
2014-01-17 8:40 ` David House
2014-01-17 9:10 ` Gabriel Scherer
2014-01-17 9:22 ` Simon Cruanes
2014-01-17 17:57 ` Gerd Stolpmann
2014-01-18 1:35 ` Jon Harrop
2014-01-19 6:19 ` oleg
2014-01-21 1:51 ` Francois Berenger
2014-01-18 1:01 ` Jon Harrop
2014-01-24 10:06 ` Alain Frisch
2014-01-24 10:16 ` Alain Frisch
2014-01-24 13:32 ` Yaron Minsky
[not found] ` <CAK=fH+jfi=GsMYBZzmuo=V5UAWimyxiiamY2+DkLg6F0i8XHGw@mail.gmail.com>
2014-01-17 9:11 ` David House
2014-01-17 11:23 ` Jonathan Kimmitt
2014-01-17 13:46 ` Nicolas Braud-Santoni
2014-01-17 13:56 ` Frédéric Bour
2014-01-17 14:02 ` Yaron Minsky
2014-01-17 14:09 ` Simon Cruanes
2014-01-17 22:52 ` Yaron Minsky
2014-01-18 1:37 ` Jon Harrop
2014-01-17 14:24 ` Gabriel Scherer
2014-01-17 22:29 ` Yaron Minsky
2014-01-18 1:27 ` Jon Harrop
2014-01-18 1:18 ` Jon Harrop
2014-01-20 10:16 ` Goswin von Brederlow
2014-01-20 11:23 ` Jonathan Kimmitt
2014-01-21 2:05 ` Francois Berenger
2014-01-22 21:22 ` Jon Harrop
2014-01-22 21:26 ` Jon Harrop
2014-01-23 9:29 ` Goswin von Brederlow
2014-01-23 23:20 ` Jon Harrop
2014-01-23 23:28 ` Yotam Barnoy
2014-01-24 8:22 ` Jon Harrop
2014-01-24 8:34 ` Andreas Rossberg
2014-01-24 16:56 ` Jon Harrop
2014-01-27 15:29 ` Goswin von Brederlow
2014-01-27 16:18 ` Yotam Barnoy
2014-01-29 7:56 ` Goswin von Brederlow
2014-01-29 8:32 ` Jon Harrop
2014-01-29 16:11 ` Yotam Barnoy
2014-01-30 18:43 ` Yotam Barnoy
2014-02-01 15:58 ` Goswin von Brederlow
2014-01-30 21:31 ` Jon Harrop
2014-01-30 21:43 ` Yotam Barnoy
2014-01-31 8:26 ` Jon Harrop
2014-02-01 15:40 ` Goswin von Brederlow
2014-01-27 10:03 ` Goswin von Brederlow
2014-01-17 14:36 ` Markus Mottl
2014-01-17 15:49 ` Yotam Barnoy [this message]
2014-01-17 16:22 ` Markus Mottl
2014-01-20 10:09 ` Goswin von Brederlow
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='CAN6ygO=USdGy8LguaMdK-fL30bomgQiuUaYSEewdF=tohXcgkw@mail.gmail.com' \
--to=yotambarnoy@gmail.com \
--cc=alphablock@orange.fr \
--cc=caml-list@inria.fr \
--cc=markus.mottl@gmail.com \
/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