From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: "lwn" <lwn@lwn.net>, "cwn" <cwn@lists.idyll.org>, caml-list@inria.fr
Subject: [Caml-list] Attn: Development Editor, Latest OCaml Weekly News
Date: Tue, 31 May 2022 14:29:41 +0200 [thread overview]
Message-ID: <87czftsx56.fsf@m4x.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 4673 bytes --]
Hello
Here is the latest OCaml Weekly News, for the week of May 24 to 31,
2022.
Table of Contents
─────────────────
carray.0.0.1
OCaml Users and Developers Workshop 2022
Old CWN
carray.0.0.1
════════════
Archive: <https://discuss.ocaml.org/t/ann-carray-0-0-1/9938/1>
Danny Willems announced
───────────────────────
I'm glad to announce the first (experimental) release of ocaml-carray,
a library mocking the Array interface to work with contiguous C array.
*Disclaimer*: this first version is experimental and must be used with
caution. A restricted set of values are supported at the moment
(custom block with no out-of-heap values). Depending on the demand,
more values might be supported. Feel free to use this thread to
suggest ideas, make opinions, etc.
Repository
<https://gitlab.com/dannywillems/ocaml-carray>
License
[MIT]
Release
[0.0.1]
Documentation
<https://dannywillems.gitlab.io/ocaml-carray/carray/index.html>
Nomadic Labs website
<https://nomadic-labs.com>
Tezos ZK-rollups repository
<https://gitlab.com/nomadic-labs/privacy-team>
[MIT]
<https://gitlab.com/dannywillems/ocaml-carray/-/blob/0.0.1/LICENSE>
[0.0.1] <https://gitlab.com/dannywillems/ocaml-carray/-/tags/0.0.1>
Motivation
╌╌╌╌╌╌╌╌╌╌
OCaml arrays are not always contiguous piece of memory, requiring
accessing different chunks of memory when accessing individual
elements. When requiring a value in memory, the CPU will fetch the RAM
and load not only the particular value but a memory page (a contiguous
piece of memory) and add it to its cache. The CPU will use its cache
to load the values in its registers. It is not efficient with large
OCaml arrays as the CPU will constantly fetch the RAM to load
different memory pages in its cache. Also, when using the C FFI, the
user must know the memory representation of an array and use the non
user-friendly low-level interface macro `Field'.
This work
╌╌╌╌╌╌╌╌╌
This library provides a polymorphic interface mocking a subset of the
`Array' interface to work with contiguous piece of memory. Using the
library should be as easy as adding `module Array = Carray'. A C
macro `Carray_val' is also provided for developers writing bindings
and requires to simply cast in the underlying C type. It has also
been observed sub arrays are sometimes used for read-only
operations. However, `Array.sub' allocates a fresh copy of the
requested sub part. `Carray' leverages this memory cost by providing
noalloc variants, like `sub_noalloc'.
Performances
╌╌╌╌╌╌╌╌╌╌╌╌
The concept has been tested and used in real world applications like
the polynomial library used by Nomadic Labs to implement zk-rollups. A
speed up of around 50% has been observed when using contiguous arrays
compared to OCaml arrays to compute NTT/FFT.
Usage
╌╌╌╌╌
This library is *experimental*. Use this library with caution. The
interface might change in the future.
┌────
│ opam install carray.0.0.1
└────
OCaml Users and Developers Workshop 2022
════════════════════════════════════════
Archive:
<https://discuss.ocaml.org/t/ocaml-users-and-developers-workshop-2022/9726/2>
Continuing this thread, Matija Pretnar announced
────────────────────────────────────────────────
This is a reminder for anyone interested in contributing to OCaml
Workshop 2022. The deadline has been slightly extended to Friday, June
3 (anywhere on Earth), which means you have roughly *four days left*
to prepare your submissions.
Old CWN
═══════
If you happen to miss a CWN, you can [send me a message] and I'll mail
it to you, or go take a look at [the archive] or the [RSS feed of the
archives].
If you also wish to receive it every week by mail, you may subscribe
[online].
[Alan Schmitt]
[send me a message] <mailto:alan.schmitt@polytechnique.org>
[the archive] <https://alan.petitepomme.net/cwn/>
[RSS feed of the archives] <https://alan.petitepomme.net/cwn/cwn.rss>
[online] <http://lists.idyll.org/listinfo/caml-news-weekly/>
[Alan Schmitt] <https://alan.petitepomme.net/>
[-- Attachment #2: Type: text/html, Size: 14261 bytes --]
next reply other threads:[~2022-05-31 12:29 UTC|newest]
Thread overview: 112+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 12:29 Alan Schmitt [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-26 17:54 Alan Schmitt
2022-07-19 8:58 Alan Schmitt
2022-07-12 7:59 Alan Schmitt
2022-07-05 7:42 Alan Schmitt
2022-06-28 7:37 Alan Schmitt
2022-06-21 8:06 Alan Schmitt
2022-06-14 9:29 Alan Schmitt
2022-06-07 10:15 Alan Schmitt
2022-05-24 8:04 Alan Schmitt
2022-05-17 7:12 Alan Schmitt
2022-05-10 12:30 Alan Schmitt
2022-05-03 9:11 Alan Schmitt
2022-04-26 6:44 Alan Schmitt
2022-04-19 5:34 Alan Schmitt
2022-04-12 8:10 Alan Schmitt
2022-04-05 11:50 Alan Schmitt
2022-03-29 7:42 Alan Schmitt
2022-03-22 13:01 Alan Schmitt
2022-03-15 9:59 Alan Schmitt
2022-03-01 13:54 Alan Schmitt
2022-02-22 12:43 Alan Schmitt
2022-02-08 13:16 Alan Schmitt
2022-02-01 13:00 Alan Schmitt
2022-01-25 12:44 Alan Schmitt
2022-01-11 8:20 Alan Schmitt
2022-01-04 7:56 Alan Schmitt
2021-12-28 8:59 Alan Schmitt
2021-12-21 9:11 Alan Schmitt
2021-12-14 11:02 Alan Schmitt
2021-11-30 10:51 Alan Schmitt
2021-11-16 8:41 Alan Schmitt
2021-11-09 10:08 Alan Schmitt
2021-11-02 8:50 Alan Schmitt
2021-10-19 8:23 Alan Schmitt
2021-09-28 6:37 Alan Schmitt
2021-09-21 9:09 Alan Schmitt
2021-09-07 13:23 Alan Schmitt
2021-08-24 13:44 Alan Schmitt
2021-08-17 6:24 Alan Schmitt
2021-08-10 16:47 Alan Schmitt
2021-07-27 8:54 Alan Schmitt
2021-07-20 12:58 Alan Schmitt
2021-07-06 12:33 Alan Schmitt
2021-06-29 12:24 Alan Schmitt
2021-06-22 9:04 Alan Schmitt
2021-06-01 9:23 Alan Schmitt
2021-05-25 7:30 Alan Schmitt
2021-05-11 14:47 Alan Schmitt
2021-05-04 8:57 Alan Schmitt
2021-04-27 14:26 Alan Schmitt
2021-04-20 9:07 Alan Schmitt
2021-04-06 9:42 Alan Schmitt
2021-03-30 14:55 Alan Schmitt
2021-03-23 9:05 Alan Schmitt
2021-03-16 10:31 Alan Schmitt
2021-03-09 10:58 Alan Schmitt
2021-02-23 9:51 Alan Schmitt
2021-02-16 13:53 Alan Schmitt
2021-02-02 13:56 Alan Schmitt
2021-01-26 13:25 Alan Schmitt
2021-01-19 14:28 Alan Schmitt
2021-01-12 9:47 Alan Schmitt
2021-01-05 11:22 Alan Schmitt
2020-12-29 9:59 Alan Schmitt
2020-12-22 8:48 Alan Schmitt
2020-12-15 9:51 Alan Schmitt
2020-12-01 8:54 Alan Schmitt
2020-11-03 15:15 Alan Schmitt
2020-10-27 8:43 Alan Schmitt
2020-10-20 8:15 Alan Schmitt
2020-10-06 7:22 Alan Schmitt
2020-09-29 7:02 Alan Schmitt
2020-09-22 7:27 Alan Schmitt
2020-09-08 13:11 Alan Schmitt
2020-09-01 7:55 Alan Schmitt
2020-08-18 7:25 Alan Schmitt
2020-07-28 16:57 Alan Schmitt
2020-07-21 14:42 Alan Schmitt
2020-07-14 9:54 Alan Schmitt
2020-07-07 10:04 Alan Schmitt
2020-06-30 7:00 Alan Schmitt
2020-06-16 8:36 Alan Schmitt
2020-06-09 8:28 Alan Schmitt
2020-05-19 9:52 Alan Schmitt
2020-05-12 7:45 Alan Schmitt
2020-05-05 7:45 Alan Schmitt
2020-04-28 12:44 Alan Schmitt
2020-04-21 8:58 Alan Schmitt
2020-04-14 7:28 Alan Schmitt
2020-04-07 7:51 Alan Schmitt
2020-03-31 9:54 Alan Schmitt
2020-03-24 9:31 Alan Schmitt
2020-03-17 11:04 Alan Schmitt
2020-03-10 14:28 Alan Schmitt
2020-03-03 8:00 Alan Schmitt
2020-02-25 8:51 Alan Schmitt
2020-02-18 8:18 Alan Schmitt
2020-02-04 8:47 Alan Schmitt
2020-01-28 10:53 Alan Schmitt
2020-01-21 14:08 Alan Schmitt
2020-01-14 14:16 Alan Schmitt
2020-01-07 13:43 Alan Schmitt
2019-12-31 9:18 Alan Schmitt
2019-12-17 8:52 Alan Schmitt
2019-12-10 8:21 Alan Schmitt
2019-12-03 15:42 Alan Schmitt
2019-11-26 8:33 Alan Schmitt
2019-11-12 13:21 Alan Schmitt
2019-11-05 6:55 Alan Schmitt
2019-10-15 7:28 Alan Schmitt
2019-09-03 7:35 Alan Schmitt
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=87czftsx56.fsf@m4x.org \
--to=alan.schmitt@polytechnique.org \
--cc=caml-list@inria.fr \
--cc=cwn@lists.idyll.org \
--cc=lwn@lwn.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).