Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Christophe Raffalli <christophe@raffalli.eu>
To: Florian Angeletti <florian.angeletti@inria.fr>, caml-list@inria.fr
Subject: [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 14:07:22 -1000	[thread overview]
Message-ID: <20211009000722.otsy76prtixl226t@oulala> (raw)
In-Reply-To: <20211008203420.krbaicozculplmfk@oulala>

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


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: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2021-10-09  0:07 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   ` Christophe Raffalli [this message]
2021-10-09  0:58     ` [Caml-list] Sequential speed 4.12.0 vs 4.13.1 vs multicore (Was: The road to OCaml 5.0) Michael Bacarella
2021-10-09  1:11       ` Michael Bacarella
2021-10-09  1:20         ` Michael Bacarella
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=20211009000722.otsy76prtixl226t@oulala \
    --to=christophe@raffalli.eu \
    --cc=caml-list@inria.fr \
    --cc=florian.angeletti@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