Reducing Message Latency and CPU Utilization in the CAF Actor Framework

Massimo Torquati, Tullio Menga, Tiziano De Matteis, Daniele De Sensi, Gabriele Mencagli

Research output: Chapter in Book / Report / Conference proceedingConference contributionAcademicpeer-review

Abstract

In this work, we consider the C++ Actor Framework (CAF), a recent proposal that revamped the interest in building concurrent and distributed applications using the actor programming model in C++. CAF has been optimized for high-throughput computing, whereas message latency between actors is greatly influenced by the message data rate: At low and moderate rates the latency is higher than at high data rates. To this end, we propose a modification of the polling strategies in the work-stealing CAF scheduler, which can reduce message latency at low and moderate data rates up to two orders of magnitude without compromising the overall throughput and message latency at maximum pressure. The technique proposed uses a lightweight event notification protocol that is general enough to be used used to optimize the runtime of other frameworks experiencing similar issues.
Original languageEnglish
Title of host publicationProceedings - 26th Euromicro International Conference on Parallel, Distributed, and Network-Based Processing, PDP 2018
EditorsI. Kotenko, I. Merelli, P. Lio
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages145-153
ISBN (Electronic)9781538649756
DOIs
Publication statusPublished - 6 Jun 2018
Externally publishedYes
Event26th Euromicro International Conference on Parallel, Distributed, and Network-Based Processing, PDP 2018 - Cambridge, United Kingdom
Duration: 21 Mar 201823 Mar 2018

Conference

Conference26th Euromicro International Conference on Parallel, Distributed, and Network-Based Processing, PDP 2018
Country/TerritoryUnited Kingdom
CityCambridge
Period21/03/1823/03/18

Fingerprint

Dive into the research topics of 'Reducing Message Latency and CPU Utilization in the CAF Actor Framework'. Together they form a unique fingerprint.

Cite this