From: Michael Bacarella <firstname.lastname@example.org> To: Christophe Raffalli <email@example.com> Cc: Florian Angeletti <firstname.lastname@example.org>, email@example.com Subject: Re: [Caml-list] Sequential speed 4.12.0 vs 4.13.1 vs multicore (Was: The road to OCaml 5.0) Date: Fri, 8 Oct 2021 18:20:27 -0700 [thread overview] Message-ID: <CAK58AGG-W3_RAGZB5N1pK0fUDuqH-FAYDoyvFyi6ZB2oUtjdsQ@mail.gmail.com> (raw) In-Reply-To: <CAK58AGEcB7CiSBFz8B+Gh8i=93E9YSgayCUSaxy-Cj9T27GKBQ@mail.gmail.com> [-- Attachment #1: Type: text/plain, Size: 1894 bytes --] Oh. Or I'm just out of date. Apparently the way you choose compilers options (like flambda) in a switch changed awhile ago: https://discuss.ocaml.org/t/experimental-new-layout-for-the-ocaml-variants-packages-in-opam-repository/6779 Sorry about the noise! On Fri, Oct 8, 2021 at 6:11 PM Michael Bacarella < firstname.lastname@example.org> wrote: > Sorry, you actually said as much "On the same examples, same options *(flambda > everywhere)*," > > Though, the expectation that was thwarted for me is that there's no > specific multicore flambda switch. Just multicore. And that 20-25% speedup > felt like a familiar we-switched-to-flambda speedup to me. > > On Fri, Oct 8, 2021 at 5:58 PM Michael Bacarella < > email@example.com> wrote: > >> My gut here says you're unwittingly comparing regular ocaml to flambda >> ocaml. >> >> https://ocaml.org/manual/flambda.html >> >> Perhaps multicore only comes in flambda flavor now (I notice it's not >> available as a switch). >> >> On Fri, Oct 8, 2021 at 5:07 PM Christophe Raffalli < >> firstname.lastname@example.org> wrote: >> >>> >>> Hello, >>> >>> I managed to install ocaml 4.12.0 with multicore. I could not >>> parallelise my >>> code in 5mn ;-) but I check just the sequential speed and got a bit >>> surprised. On the same examples, same options (flambda everywhere), etc >>> ... >>> >>> Ex 1 Ex 2 Ex 3 >>> 4.13.1 normal 45s 12s 49s >>> 4.12.0 normal 36s 11s 45s >>> 4.12.0 multicore 31s 10s 40s >>> >>> These are not small differences and it is rather surprising that >>> >>> 4.13.1 is significantly slower than 4.12.0 (20 to 25%) >>> >>> 4.12.0 + multicore is faster on sequential code. >>> >>> Other people observe the same ? >>> Any idea ? Should I report an issue for the speed degradation of 4.13.1 ? >>> >>> Christophe >>> >> [-- Attachment #2: Type: text/html, Size: 3181 bytes --]
next prev parent reply other threads:[~2021-10-09 1:21 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-07 9:48 [Caml-list] The road to OCaml 5.0 Florian Angeletti 2021-10-08 1:42 ` Francois Berenger 2021-10-08 20:34 ` Christophe Raffalli 2021-10-09 0:07 ` [Caml-list] Sequential speed 4.12.0 vs 4.13.1 vs multicore (Was: The road to OCaml 5.0) Christophe Raffalli 2021-10-09 0:58 ` Michael Bacarella 2021-10-09 1:11 ` Michael Bacarella 2021-10-09 1:20 ` Michael Bacarella [this message] 2021-10-09 2:10 ` Christophe Raffalli 2021-10-09 17:20 ` Xavier Leroy 2021-10-10 3:37 ` Christophe Raffalli 2021-10-09 17:14 ` ygrek
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=CAK58AGG-W3_RAGZB5N1pK0fUDuqH-FAYDoyvFyi6ZB2oUtjdsQ@mail.gmail.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [Caml-list] Sequential speed 4.12.0 vs 4.13.1 vs multicore (Was: The road to OCaml 5.0)' \ /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
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).