caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Yaron Minsky <yminsky@janestreet.com>
To: David Allsopp <dra-news@metastack.com>
Cc: Helmut Brandl <helmut.brandl@gmx.net>, caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Performance penalty for using monad
Date: Sun, 24 Sep 2017 07:28:29 -0400	[thread overview]
Message-ID: <CACLX4jR7JS=uOFsEhjDDHK76WBHh2NANT2dWs_-SaHmMTf4Zcg@mail.gmail.com> (raw)
In-Reply-To: <E51C5B015DBD1348A1D85763337FB6D9014D75D013@Remus.metastack.local>

[-- Attachment #1: Type: text/plain, Size: 2090 bytes --]

On Sun, Sep 24, 2017 at 5:22 AM, David Allsopp <dra-news@metastack.com>
wrote:

> Helmut Brandl wrote:
> > One more question: It seems that flambda is necessary in order to
> optimize
> > monadic code. Is there a plan that flambda will be included in a base
> > release of ocaml?
> >
> > Up to now all base releases like 4.03.0, 4.04.0, etc. do not include
> > flambda. I have to request the extension if I want it.
>
> flambda work is still ongoing (work-in-progress sounds a bit mean - it's
> more that it's still evolving!) and it's not yet in a position to be
> enabled by default. This is the ultimate plan, though there is no nominated
> version at which we yet expect to make it the default.


For what it's worth, the main blocker for us turning Flambda on by default
in classic mode is getting build artifact size and compilation speed down
basically to the same level as closure-compilation. We're getting pretty
close to that goal, though it will take a bit more time to get the
improvements in question upstreamed.

So getting Flambda enabled by default isn't that far away (though most of
the real benefits will require -O3, which will still lengthen compilation
by quite a bit.)


>
> Jesper Louis Anderson wrote:
> > That decoder used monads heavily as well, and flambda provided roughly
> > an order of magnitude speedup (and a lower GC pressure as well in
> addition).
> > It was enough that I made a mental note of using flambda if this ever
> went
> > into a system with high throughput requirements.
>
> Just for added interest, there are things being worked on in opam 2 which
> should allow you to be able to declare such a package as either needing an
> OCaml compiler with flambda enabled or which would let you display a
> warning message if the package is installed in a compiler which doesn't
> have flambda enabled.
>
>
> David
>
> --
> 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: 3102 bytes --]

  reply	other threads:[~2017-09-24 11:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-18 15:23 Helmut Brandl
2017-09-18 15:31 ` Yotam Barnoy
2017-09-19 12:46   ` Helmut Brandl
2017-09-19 13:24     ` Jesper Louis Andersen
2017-09-19 16:33       ` Helmut Brandl
2017-09-24  9:22         ` David Allsopp
2017-09-24 11:28           ` Yaron Minsky [this message]
2017-09-24 20:04             ` Josh Berdine
2017-09-25  8:32               ` Mark Shinwell
2017-09-25  9:25                 ` Josh Berdine

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='CACLX4jR7JS=uOFsEhjDDHK76WBHh2NANT2dWs_-SaHmMTf4Zcg@mail.gmail.com' \
    --to=yminsky@janestreet.com \
    --cc=caml-list@inria.fr \
    --cc=dra-news@metastack.com \
    --cc=helmut.brandl@gmx.net \
    /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).