From: Jesper Louis Andersen <jesper.louis.andersen@gmail.com>
To: Laurent Mazare <laurent.mazare@gmail.com>
Cc: Milo Davis <davis.mil@husky.neu.edu>,
Francois Berenger <francois.berenger@inria.fr>,
Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Tensorflow bindings for OCaml
Date: Wed, 30 Mar 2016 17:12:24 +0200 [thread overview]
Message-ID: <CAGrdgiWxPmHsTunJYtZHnCzXMS3bt24NdfiqB1uxcw4LZ6CB6Q@mail.gmail.com> (raw)
In-Reply-To: <CAObQTrV+7eArahiOjfn8gQkwZDuUKaF63Qa4uNZ4N5ex5zrdeQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
On Tue, Mar 29, 2016 at 6:01 PM, Laurent Mazare <laurent.mazare@gmail.com>
wrote:
> We've started putting together some TensorFlow bindings for OCaml.
>
Excellent news!
I've built most of an Erlang/OCaml layer so you can run OCaml programs as
computation engines as were they Erlang port programs. Most base-types have
been verified through QuickCheck, though I still need to improve the code a
bit with some refactoring.
If you pipeline messages, the processing roundtrip is around 1.2 million
requests per second on my machine, which is quite fine in most cases. The
overhead of sending the request to OCaml is around 1000 nanos. And this is
without optimization I might add. The overhead is about the same if you
move the computation to a dirty scheduler inside the Erlang node, so if you
can work with the pipelining overhead, it is not too shabby. Of course the
number is worse if you actually do some computation on the OCaml side, but
that is the purpose of it all. At 1000 nanos or less, the feasibility of
computing in OCaml just went up.
Tensorflow in OCaml was next on my TODO list for these kinds of things, but
I would much rather use these bindings than writing my own :)
--
J.
[-- Attachment #2: Type: text/html, Size: 1822 bytes --]
prev parent reply other threads:[~2016-03-30 15:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 2:19 Milo Davis
2016-03-10 15:05 ` Francois Berenger
2016-03-10 17:43 ` Milo Davis
2016-03-10 17:54 ` Travis
2016-03-10 19:58 ` Jesper Louis Andersen
2016-03-29 16:01 ` Laurent Mazare
2016-03-30 15:12 ` Jesper Louis Andersen [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=CAGrdgiWxPmHsTunJYtZHnCzXMS3bt24NdfiqB1uxcw4LZ6CB6Q@mail.gmail.com \
--to=jesper.louis.andersen@gmail.com \
--cc=caml-list@inria.fr \
--cc=davis.mil@husky.neu.edu \
--cc=francois.berenger@inria.fr \
--cc=laurent.mazare@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