From: "Jon Harrop" <jon@ffconsultancy.com>
To: "'oliver'" <oliver@first.in-berlin.de>, <caml-list@inria.fr>
Subject: RE: [Caml-list] Case study in optimization: porting a compiler from OCaml to F#
Date: Wed, 13 Mar 2013 20:00:27 -0000 [thread overview]
Message-ID: <011001ce2025$691e3830$3b5aa890$@ffconsultancy.com> (raw)
In-Reply-To: <20130313182745.GC3814@siouxsie>
Oliver wrote:
> What is missing, is the information, how many cores / processors the machine
> has, on which the F# code runs, and if the OCaml code runs on the same machine.
Benchmark measurements used for comparison between OCaml and F# were always done on the same machine running Windows. I used two machines:
* 2-core 1.67GHz Intel Atom N570 based netbook.
* 8-core 2.0GHz Intel Xeon E5405 based workstation.
The client verified the relative performance on their own machines.
> What about Ocaml Byteocde vs. Nativecode?
The performance comparison was done using native code. We did not benchmark OCaml bytecode.
> And what, if the re-designt program would be back-ported to OCaml?
Only minor changes were made, no redesign. Some of those changes could be back-ported to the OCaml but there is no motivation to do so.
Cheers,
Jon.
-----Original Message-----
From: caml-list-request@inria.fr [mailto:caml-list-request@inria.fr] On Behalf Of oliver
Sent: 13 March 2013 18:28
To: caml-list@inria.fr
Subject: Re: [Caml-list] Case study in optimization: porting a compiler from OCaml to F#
Hello Jon,
thanks for your report.
Very interesting.
On Wed, Mar 13, 2013 at 05:04:26PM -0000, Jon Harrop wrote:
[...]
> After demonstrating the correctness of the translation, my effort
> turned to trying to improve performance in an attempt to compete with
> the original OCaml code. I had believed that this could well prove to
> be prohibitively difficult or even impossible because symbolic code is OCaml's main strength.
> However, I have managed to make the F# around 8x faster than it was
> and, in particular, substantially faster than the original OCaml.
[...]
What is missing, is the information, how many cores / processors the machine has, on which the F# code runs, and if the OCaml code runs on the same machine.
What about Ocaml Byteocde vs. Nativecode?
And what, if the re-designt program would be back-ported to OCaml?
Ciao,
Oliver
--
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
prev parent reply other threads:[~2013-03-13 20:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 17:04 Jon Harrop
2013-03-13 17:14 ` julien verlaguet
2013-03-13 19:19 ` Jon Harrop
2013-03-13 19:28 ` oliver
2013-03-14 15:05 ` oliver
2013-03-14 15:15 ` oliver
2013-03-15 13:34 ` Pierre-Alexandre Voye
2013-03-17 12:06 ` Jon Harrop
2013-03-19 1:50 ` Francois Berenger
2013-03-20 20:54 ` Jon Harrop
2013-03-20 22:35 ` Roberto Di Cosmo
2013-03-21 4:13 ` Mike Lin
2013-03-21 7:35 ` Roberto Di Cosmo
2013-03-21 20:07 ` Roberto Di Cosmo
2013-03-19 12:47 ` Jean-Marc Alliot
2013-03-20 9:32 ` Roberto Di Cosmo
2013-03-19 1:37 ` Francois Berenger
2013-03-13 17:55 ` Alain Frisch
2013-03-13 19:44 ` Jon Harrop
2013-03-13 21:02 ` Alain Frisch
2013-03-13 18:27 ` oliver
2013-03-13 20:00 ` Jon Harrop [this message]
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='011001ce2025$691e3830$3b5aa890$@ffconsultancy.com' \
--to=jon@ffconsultancy.com \
--cc=caml-list@inria.fr \
--cc=oliver@first.in-berlin.de \
/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).