https://github.com/pmatos/racket-loci

Implementation of local and remote loci for Racket
https://github.com/pmatos/racket-loci

parallelism processes racket

Last synced: 25 days ago
JSON representation

Implementation of local and remote loci for Racket

• Host: GitHub
• URL: https://github.com/pmatos/racket-loci
• Owner: pmatos
• License: lgpl-3.0
• Created: 2018-10-06T09:46:00.000Z (over 6 years ago)
• Default Branch: master
• Last Pushed: 2021-01-08T14:22:40.000Z (about 4 years ago)
• Last Synced: 2024-11-10T00:44:51.496Z (3 months ago)
• Topics: parallelism, processes, racket
• Language: Racket
• Size: 478 KB
• Stars: 12
• Watchers: 7
• Forks: 2
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • Funding: .github/FUNDING.yml
  • License: LICENSE

Awesome Lists containing this project

README

        
[![CI](https://github.com/pmatos/racket-loci/workflows/CI/badge.svg?branch=master)](https://github.com/pmatos/racket-loci/actions)

[![Scribble](https://img.shields.io/badge/Docs-Scribble-blue.svg)](https://pmatos.github.io/racket-loci)

# racket-loci 

Implementation of local and remote loci for Racket.

> **locus** (noun)

> pl. *loci*

> 

> Definition of locus 

> 1. the place where something is situated or occurs

> 

> from [Merriam-Webster Dictionary](https://www.merriam-webster.com/dictionary/locus)

This library implements `loci`, which resemble racket `places` but do not have the same problematic behaviour as `places` when used on many-core machines. `places` are based on OS threads, while `loci` are based on OS processes. The reason to implement `loci` is that `places` do not scale above 12 core machines due to memory allocation locking. More information can be found in the [mailing list](https://groups.google.com/d/msg/racket-users/oE72JfIKDO4/zbFI6knhAQAJ).

A `locus` is a distinct racket instance running on a different process communicating via OS pipes. Hopefully there will be more documentation soon... this is still the early stages and this library **is not yet usable**. Happy to receive questions, comments, complaints and pull requests.

Most of this work was inspired on the implementation of racket places from which ideas and code were copied shamelessly. Thanks to the original authors.

## Future Work

* Implement remote loci