caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: "lwn" <lwn@lwn.net>, "cwn"  <cwn@lists.idyll.org>,
	caml-list@inria.fr, comp@lists.orbitalfox.eu
Subject: [Caml-list] Attn: Development Editor, Latest OCaml Weekly News
Date: Tue, 03 Mar 2020 09:00:21 +0100	[thread overview]
Message-ID: <87r1y96f6y.fsf@polytechnique.org> (raw)

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

Here is the latest OCaml Weekly News, for the week of February 25 to
March 03, 2020.

Table of Contents
─────────────────

OCaml 4.10 released
Summary of the Dune retreat 2020
Multicore OCaml: Feb 2020 update
Oplot 0.50
soupault: a static website generator based on HTML rewriting
Old CWN


OCaml 4.10 released
═══════════════════

  Archive: <https://discuss.ocaml.org/t/ocaml-4-10-released/5194/4>


Contnuing this thread, Anil Madhavapeddy said
─────────────────────────────────────────────

  Indeed, many thanks to everyone who leapt in to make 4.10 ready in
  opam in such record time!  Just a note that the CI Docker images are
  now also rebuilt for x86_64, arm32/64 and ppc64le to reflect the 4.10
  release, so feel free to start using
  them. <https://hub.docker.com/r/ocaml/opam2/tags>


Summary of the Dune retreat 2020
════════════════════════════════

  Archive:
  <https://discuss.ocaml.org/t/summary-of-the-dune-retreat-2020/5224/1>


Jérémie Dimino announced
────────────────────────

  We recently organised the second Dune retreat. If you'd like to see
  what is happening in the Dune world at the moment, please find a
  summary of what we discussed and work on in this blog post!

  <https://dune.build/blog/dune-retreat-2020/>


Multicore OCaml: Feb 2020 update
════════════════════════════════

  Archive:
  <https://discuss.ocaml.org/t/multicore-ocaml-feb-2020-update/5227/1>


Anil Madhavapeddy announced
───────────────────────────

  Welcome to the February 2020 news update from the Multicore OCaml
  team, spread across the UK, India, France and Switzerland! This
  follows on from [last month's] update, and has been put together by
  @shakthimaan and @kayceesrk.

  The [release of OCaml 4.10.0] has successfully pushed out some
  prerequisite features into the upstream compiler.  Our work in
  February has focussed on getting the multicore OCaml branch "feature
  complete" with respect to the complete OCaml language, and doing
  extensive benchmarking and stress testing to test our two minor heap
  implementations.

  To this end, a number of significant patches have been merged into the
  [Multicore OCaml trees] that essentially provide complete coverage of
  the language features. We encourage you to test the same for
  regressions and provide any improvements or report shortcomings to
  us. There are ongoing OCaml PRs and issues that are also under review,
  and we hope to complete those for the 4.11 release cycle. A new set of
  parallel benchmarks have been added to our [Sandmark benchmarking
  suite] (live instance [here]), including enhancements to the build
  setup.


[last month's]
<https://discuss.ocaml.org/t/multicore-ocaml-january-2020-update/5090>

[release of OCaml 4.10.0]
<https://discuss.ocaml.org/t/ocaml-4-10-released/5194>

[Multicore OCaml trees]
<https://github.com/ocaml-multicore/ocaml-multicore>

[Sandmark benchmarking suite] <https://github.com/ocaml-bench/sandmark>

[here] <http://bench2.ocamllabs.io>

Multicore OCaml
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

◊ Completed

  The following PRs have been merged into Multicore OCaml:

  • [ocaml-multicore/ocaml-multicore#281] Introduce `Forcing_tag' to fix
    concurrency bug with lazy values

    A `Forcing_tag' is used to implement lazy values to handle a
    concurrency bug. It behaves like a locked bit, and any concurrent
    access by a mutator will raise an exception on that domain.

  • [ocaml-multicore/ocaml-multicore#282] Safepoints

    A preliminary version of safe points has been merged into the
    Multicore OCaml trees. [ocaml-multicore/ocaml-multicore#187] also
    contains more discussion and background about how coverage can be
    improved in future PRs.

  • [ocaml-multicore/ocaml-multicore#285] Introduce an 'opportunistic'
    major collection slice

    An "opportunistic work credit" is implemented in this PR which forms
    a basis for doing mark and sweep work while waiting to synchronise
    with other domains.

  • [ocaml-multicore/ocaml-multicore#286] Do fflush and variable args in
    caml_gc_log

    The caml_gc_log() function has been updated to ensure that `fflush'
    is invoked only when GC logging is enabled.

  • [ocaml-multicore/ocaml-multicore#287] Increase EVENT_BUF_SIZE

    During debugging with event trace data it is useful to reduce the
    buffer flush times, and hence the `EVENT_BUF_SIZE' has now been
    increased.

  • [ocaml-multicore/ocaml-multicore#288] Write barrier optimization

    This PR closes the regression for the `chameneos_redux_lwt'
    benchmarking in Sandmark by using `intnat' to avoid sign extensions
    and cleans up `write_barrier' to improve overall performance.

  • [ocaml-multicore/ocaml-multicore#290] Unify sweep budget to be in
    word size

    The PR updates the sweep work units to all be in word size. This is
    to handle the differences between the budget for setup, sweep and
    for large allocations in blocks.


  [ocaml-multicore/ocaml-multicore#281]
  <https://github.com/ocaml-multicore/ocaml-multicore/pull/281>

  [ocaml-multicore/ocaml-multicore#282]
  <https://github.com/ocaml-multicore/ocaml-multicore/pull/282>

  [ocaml-multicore/ocaml-multicore#187]
  <https://github.com/ocaml-multicore/ocaml-multicore/issues/187>

  [ocaml-multicore/ocaml-multicore#285]
  <https://github.com/ocaml-multicore/ocaml-multicore/pull/285>

  [ocaml-multicore/ocaml-multicore#286]
  <https://github.com/ocaml-multicore/ocaml-multicore/pull/286>

  [ocaml-multicore/ocaml-multicore#287]
  <https://github.com/ocaml-multicore/ocaml-multicore/pull/287>

  [ocaml-multicore/ocaml-multicore#288]
  <https://github.com/ocaml-multicore/ocaml-multicore/pull/288>

  [ocaml-multicore/ocaml-multicore#290]
  <https://github.com/ocaml-multicore/ocaml-multicore/pull/290>


◊ Ongoing

  • A lot of work is ongoing for the implementation of a synchronised
    minor garbage collector for Multicore OCaml, including benchmarking
    for the stop-the-world (stw) branch.  We will publish the results of
    this in a future update, as we are assembling a currently
    comprehensive evaluation of the runtime against the mainstream
    runtime.


Benchmarking
╌╌╌╌╌╌╌╌╌╌╌╌

  [Sandmark] now has support to run parallel benchmarks. We can also now
  about GC latency measurements for both stock OCaml and Multicore OCaml
  compiler.

  • [ocaml-bench/sandmark#73] More parallel benchmarks

    A number of parallel benchmarks such as N-body, Quick Sort and
    matrix multiplication have now been added to Sandmark!

  • [ocaml-bench/sandmark#76] Promote packages. Unbreak CI.

    The Continuous Integration build can now execute after updating and
    promoting packages in Sandmark.

  • [ocaml-bench/sandmark#78] Add support for collecting information
    about GC pausetimes on trunk

    The PR now helps process the runtime log and produces a `.bench'
    file that captures the GC pause times. This works on both stock
    OCaml and in Multicore OCaml.

  • [ocaml-bench/sandmark#86] Read and write Irmin benchmark

    A test for measuring Irmin's merge capabilities with Git as its
    filesystem is being tested with different read and write rates.

  • A number of other parallel benchmarks like Merge sort,
    Floyd-Warshall matrix, prime number generation, parallel map, filter
    et. al. have been added to Sandmark.


[Sandmark] <http://bench2.ocamllabs.io/>

[ocaml-bench/sandmark#73]
<https://github.com/ocaml-bench/sandmark/pull/73>

[ocaml-bench/sandmark#76]
<https://github.com/ocaml-bench/sandmark/pull/76>

[ocaml-bench/sandmark#78]
<https://github.com/ocaml-bench/sandmark/pull/78>

[ocaml-bench/sandmark#86]
<https://github.com/ocaml-bench/sandmark/pull/86>


Documentation
╌╌╌╌╌╌╌╌╌╌╌╌╌

  • Examples using domainslib and modifying Domains are currently being
    worked upon for a chapter on Parallel Programming for Multicore
    OCaml. We will release an early draft to the community for your
    feedback.


OCaml
╌╌╌╌╌

  One PR opened to OCaml this month, which fixes up the marshalling
  scheme to be multicore compatible. The complete set of [upstream
  multicore prerequisites] are labelled in the compiler issue tracker.

  • [ocaml/ocaml#9293] Use addrmap hash table for marshaling

    The hash table (addrmap) implementation from Multicore OCaml has
    been ported to upstream OCaml to avoid using GC mark bits to
    represent visitedness.


[upstream multicore prerequisites]
<https://github.com/ocaml/ocaml/labels/multicore-prerequisite>

[ocaml/ocaml#9293] <https://github.com/ocaml/ocaml/pull/9293>


Acronyms
╌╌╌╌╌╌╌╌

  • CTF: Common Trace Format
  • CI: Continuous Integration
  • GC: Garbage Collector
  • PR: Pull Request

  As always, many thanks to our fellow OCaml developers and users who
  have reviewed our code, reported bugs or otherwise assisted this
  month.


Oplot 0.50
══════════

  Archive: <https://discuss.ocaml.org/t/ann-oplot-0-50/5235/1>


sanette announced
─────────────────

  I'm happy to annouce the revival of the `oplot' library.

  If you ever wanted to quickly draw the graph of an intriguing
  mathematical function, animate it by varying a parameter, or explore a
  3D surface, without leaving your favorite programming language, then
  `oplot' is for you.

  If you're familiar with LaTeX and want to produce nice mathematical
  graphics decorated with LaTeX formulas, that you can view onscreen,
  export to images or vector graphics (pdf, eps) then `oplot' is even
  more for you!

  • Installation: `opam install oplot'
  • documentation:
    <https://sanette.github.io/oplot/oplot/Oplot/index.html>
  • source code, issues, etc: <https://github.com/sanette/oplot>

  Drawing is hardware accelerated (opengl) thanks to the venerable
  `ocamlsdl' and `lablgl' libraries. I'm glad they still work perfectly.

  Happy plotting.


soupault: a static website generator based on HTML rewriting
════════════════════════════════════════════════════════════

  Archive:
  <https://discuss.ocaml.org/t/ann-soupault-a-static-website-generator-based-on-html-rewriting/4126/12>


Daniil Baturin announced
────────────────────────

  [1.9.0] release is now available.

  • `--index-only' option that makes soupault dump the site metadata to
    JSON and stop at that
  • Metadata extraction and index generation can now be limited to
    specific pages/section/path regexes, just like widgets
  • The `preprocess_element' widget now supports a list of selectors,
    e.g. `selector = ["code", "pre code"]'.
  • Plugin API now has functions for running external programs, and some
    more element tree access functions.
  • CSS selector parse errors are now handled gracefully ([lambdasoup
    PR#31]).
  • The `title' widget now correctly removes HTML tags from the supposed
    title string and doesn't add extra whitespace (fixes by [Thomas
    Letan]).


[1.9.0] <https://soupault.neocities.org/blog/soupault-1.9.0-release/>

[lambdasoup PR#31] <https://github.com/aantron/lambdasoup/pull/31>

[Thomas Letan] <https://soap.coffee/~lthms/>


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] <http://alan.petitepomme.net/cwn/>

[RSS feed of the archives] <http://alan.petitepomme.net/cwn/cwn.rss>

[online] <http://lists.idyll.org/listinfo/caml-news-weekly/>

[Alan Schmitt] <http://alan.petitepomme.net/>


[-- Attachment #2: Type: text/html, Size: 25154 bytes --]

             reply	other threads:[~2020-03-03  8:00 UTC|newest]

Thread overview: 112+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03  8:00 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-31 12:29 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-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=87r1y96f6y.fsf@polytechnique.org \
    --to=alan.schmitt@polytechnique.org \
    --cc=caml-list@inria.fr \
    --cc=comp@lists.orbitalfox.eu \
    --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).