Skip to content
0:00 / 0:00

#ocaml#multicoreocaml#janestreet

The Saga of Multicore OCaml

Jane Street

102K subscribers • 18 videos on Hallway

YouTube
  • Recommended by 1 person: 1 in engineering communities.

Advanced. Deep dive for people who know the field.

21K views1 year ago1 recommendation

Programming languagesSystems programmingOCaml and F#Concurrency and parallelismPerformance and optimization

Engineers from Jane Street share the challenges and lessons learned from migrating their massive codebase to the multicore OCaml 5 runtime.

Jane Street is an electronic trading firm that uses low latency trading systems built in OCaml to provide liquidity to financial markets worldwide. In December 2022, after nearly a decade of development, OCaml 5.0 was released with OCaml’s first multi-core capable runtime. This was an exciting milestone, finally making it possible to write shared-memory parallel programs in OCaml. The new runtime was designed to be easy to adopt: it didn’t disturb OCaml’s FFI, and performance was meant to be only a few percentage points slower in single-core mode. Despite those promising beginnings, switching to runtime-5 within Jane Street was harder than we expected. Indeed, we've only just switched to it this year, after 2.5 years of research and engineering effort. This talk will give an overview of the problems we ran into, and what we learned from the process, including some new ideas that solved some very old problems in the design of OCaml's GC. Read the full transcript here: janestreet.com/tech-talks/the-saga-of-multicore-ocaml/

Why it's here

1 person recommends this

What people say. Recommended as an excellent, deep-dive case study on the real-world challenges of adopting a multicore runtime in production.

Moments people linked to

u/considerealizationin r/ProgrammingLanguages • Recommends

The Saga of Multicore OCaml

u/30DVolin r/ocaml • Mentions

Talk on OxCaml Just watched most of Jaron Minsky's interesting talk about the development of Multicore OCaml from Jane Street. Two things got me genuinely excited: a) They’ve split off their codebase (compiler mostly) and are marketing it under a new name. Looks like they’re finally building their own internal language - a clone like F# initially did - tailored to their needs. Respect! From my point of view, this hopefully means the fragmentation they introduced with a second standard library, etc. might go away. If that turns out to be true, good riddance! b) What really made my day though is that they don’t find Rust interesting at all.

u/turbofish_pkin r/ocaml • Mentions

On “A Path Not Taken for OxCaml”

No he didn't explicitly said it, but he implied it. I don't think he is presenting rust correctly and also in their existing codebase with normal OCaml the very performant stuff is not written in idiomatic OCaml.
4View on Reddit

u/30DVolin r/ocaml • Mentions

On “Talk on OxCaml”

Sorry for that. Those are the two main things I had in mind The reasons listed here: Why Ocaml and about Rust in the talk
3View on Reddit