esy
domainslib
Our great sponsors
esy | domainslib | |
---|---|---|
8 | 4 | |
839 | 161 | |
0.4% | 3.1% | |
9.2 | 5.8 | |
5 days ago | about 2 months ago | |
Reason | OCaml | |
GNU General Public License v3.0 or later | ISC License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
esy
-
Compiler Development: Rust or OCaml?
As someone who wrote a fair amount of Rust and OCaml code, I have to agree with the author.
While working at Routine (YC W21), I was tasked with porting our core library to iOS to minimize code duplication. This was a lucky opportunity to write something resembling a compiler: it took in schemas described with our in-house data exchange library and generated C (for FFI) and Swift code (for the end-users, i.e., iOS developers).
Since Routine uses OCaml for everything (which was a big motivator for joining the company—I wanted to see how that would work out), I wrote it in OCaml. The end result is a 3-5k LOC project. It's by no means a full compiler, but it was lots of fun to write. The language got in the way incredibly rarely. On average, it made my life a lot easier.
We did encounter our fair share of issues, mostly due to the cross-compilation tooling (we initially used esy [1], flirted with Nix, and eventually switched to opam-cross-ios [2]), third-party libraries, and intricacies of FFI. Those do take their toll on sanity.
-
OCaml 5.0 release (including multicore and effects)
What's the current status of Esy? https://github.com/esy/esy
Any plans to backport its design back to Opam?
-
2021 at OCamlPro
It's great to hear that Opam is making progress! I just wished that it would be more deeply integrated with Dune. A package manager that doesn't build is not very useful to be honest. Currently the only way to not have to care about switches and be able to clearly specify dependencies is to use the esy package manager[1] (which had lock files a while ago).
-
PR to Merge Multicore OCaml
If you start a project today I would really try to use esy (https://esy.sh/)
I actually don’t use it myself but it seems to bring the modern programming language experience to OCaml
-
Getting Started with OCaml in 2021 · Perpetually Curious Blog
Another alternative is to use esy but I'm clearly biased here....
Here is link number 1 - Previous text "esy"
-
Frustrated by lacking cross platform support (hoping to be wrong)
Alternatively, you can use esy.sh for a simpler setup/build process (it does not require running in a Cygwin shell).
-
Opam, PNPM, Node, Esy, Docker, ReactNative on 128GB Mac
Running esy does not work. Apparently, my environment does not know that it is there. Anyone know what is going on here? I have posted this in the discussion for esy@next here. I will get back to you all when I figure this out.
domainslib
-
OCaml 5.0 Alpha Release
For nested parallel computations (think Scientific Programming, where one would use OpenMP, Rust Rayon, etc), we have domainslib [1]. Eio, a direct-style, effect-based IO library is pretty competitive against Rust Tokio [2]. The performance will only get better as we get closer to the 5.0 release.
[1] https://github.com/ocaml-multicore/domainslib
[2] See the http server performance graphs at https://tarides.com/blog/2022-03-01-segfault-systems-joins-t...
-
PR to Merge Multicore OCaml
1. Domains are the unit of parallelism. A domain is essentially an OS thread with a bunch of extra runtime book-keeping data. You can use Domain.spawn (https://github.com/ocaml-multicore/ocaml-multicore/blob/5.00...) to spawn off a new domain which will run the supplied function and terminate when it finishes. This is heavyweight though, domains are expected to be long-running.
2. Domainslib is the library developed alongside multicore to aid users in exploiting parallelism. It supports nested parallelism and is pretty highly optimised (https://github.com/ocaml-multicore/domainslib/pull/29 for some graphs/numbers). The domainslib repo has some good examples: https://github.com/ocaml-multicore/domainslib/tree/master/te...
3. We've not tested against other forms of parallelism. There isn't anything stopping you exploiting SIMD in addition to parallelism from domains.
4. No, we've not compared performance by OS.
5. No plans for the multicore team to look at accelerator integration at the moment.
I've searched a bit for this and haven't been able to find a good answer. Let's say that I have m tasks that I want to run concurrently on n cores, for example handling HTTP requests or searching for something in files. I'd also like to not have to manage manually how the tasks are going to be distributed. Basically, have the same experience as when writing Go code. Is there a way to do this in multicore OCaml? I've found the task pool in domainslib [1] but I'm not sure if it's what I'm looking for.
[1]: https://github.com/ocaml-multicore/domainslib/blob/master/li...
-
The road to OCaml 5.0
[3] Domainslib -- Parallel Programming over Multicore OCaml, https://github.com/ocaml-multicore/domainslib
What are some alternatives?
opam - opam is a source-based package manager. It supports multiple simultaneous compiler installations, flexible package constraints, and a Git-friendly development workflow.
ocaml-multicore - Multicore OCaml
dune - A composable build system for OCaml.
eioio - Effects-based direct-style IO for multicore OCaml
ocaml - The core OCaml system: compilers, runtime system, base libraries
rescript-compiler - The compiler for ReScript.
fnm - 🚀 Fast and simple Node.js version manager, built in Rust
RFCs - Design discussions about the OCaml language
ocaml-interop - OCaml<->Rust FFI with an emphasis on safety.
proof-systems - The proof systems used by Mina