Transactional Actors: Communication in Transactions
Developers often require different concurrency models to fit the various concurrency needs of the different parts of their applications. Many programming languages, such as Clojure, Scala, and Haskell, cater to this need by incorporating different concurrency models. It has been shown that, in practice, developers often combine these concurrency models. However, they are often combined in an ad hoc way and the semantics of the combination is not always well-defined. The starting hypothesis of this paper is that different concurrency models need to be carefully integrated such that the properties of each individual model are still maintained.
This paper proposes one such combination, namely the combination of the actor model and software transactional memory. In this paper, we show that, while both individual models offer strong safety guarantees, these guarantees are no longer valid when they are combined. The main contribution of this paper is a novel hybrid concurrency model called transactional actors that combines both models while preserving their guarantees. This paper also presents an implementation in Clojure and an experimental evaluation of the performance of the transactional actor model.
Mon 23 OctDisplayed time zone: Tijuana, Baja California change
13:30 - 15:00
|Transactional Actors: Communication in Transactions|
Janwillem Swalens Vrije Universiteit Brussel, Belgium, Joeri De Koster Vrije Universiteit Brussel, Belgium, Wolfgang De Meuter Vrije Universiteit BrusselLink to publication DOI Pre-print
|[Position paper] How to Test your Concurrent Software: An Approach for the Selection of Testing Techniques|
|[Position paper] Declaring Lua Data Types for GPU Code Generation|
Paulo Motta Motta & SantAnna Pesquisa e Desenvolvimento
|[Position paper] Facilitating Collaboration in High Performance Computing Projects with an Interaction Room|