Multicore OCaml: November 2021 with results of code review

[sid]

@Konstantin_Olkhovski

Wow, looks like eio schedules all fibers to one domain by default and if user explicitly is willing to throw some fibers to other physical thread, they are able to do that. That’s fantastic! Golang is doing automatic scheduling of goroutines to physical threads, which is quite annoying as one has to mind races coming from physical threads literally everywhere. Opt-in threading allows the user to split the logic into asynchronous pieces each running on one physical thread (so no data races out of nowhere), and organize communication between those pieces in a thread-safe manner

So here is an example of the advantage of OCaml’s customized approach benefitting you. Golang has chosen the defaults and those defaults are not ideal as you have explained.

That is the problem with defaults. Defaults improve sharing through standardization but defaults also hurt specialization. OCaml effects will allow you to build a very customized scheduler for your program.