useR! 2022: My ‘Futureverse: Profile Parallel Code’ Slides

[This article was first published on JottR on R, and kindly contributed to R-bloggers]. (You can report issue about the content on this page here)
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.
Screenshot of Slide #18 in my presentation. A graphical time-chart representation of the events that takes place when calling the following code in R: plan(cluster, workers = 2); fs <- lapply(1:2, function(x) future(slow(x)); vs <- value(fs); There are two futures displayed in the time chart. Each future is represented by a blue, horizontal 'lifespan' bar. The second future starts slightly after the first one. Each future is evaluated in a separate worker, which is represented as pink horizontal 'evaluate' bar. The two 'lifespan' and the two 'evaluation' bars are overlapping indicating they run in parallel.
Figure 1: A time chart of logged events for two futures resolved by two parallel workers. This is a screenshot of Slide #18 in my talk.

The useR 2022 logo

Below are the slides for my Futureverse: Profile Parallel Code talk that I presented at the useR! 2022 conference online and hosted by the Department of Biostatistics at Vanderbilt University Medical Center.

Title: Futureverse: Profile Parallel Code
Speaker: Henrik Bengtsson
Session: #21: Parallel Computing, chaired by Ilias Moutsopoulos
Slides: HTML, PDF (24 slides)
Video: conference site (25 minutes starting at the 45-minute mark; requires registration) [A public Youtube video will be made available by the conference organizer a later date]


“In this presentation, I share recent enhancements that allow developers and end-users to profile R code running in parallel via the future framework. With these new, frequently requested features, we can study how and where our computational resources are used. With the help of visualization (e.g., ggplot2 and Shiny), we can identify bottlenecks in our code and parallel setup. For example, if we find that some parallel workers are more idle than expected, we can tweak settings to improve the overall CPU utilization and thereby increase the total throughput and decrease the turnaround time (latency). These new benchmarking tools work out of the box on existing code and packages that build on the future package, including future.apply, furrr, and doFuture.

The future framework, available on CRAN since 2016, has been used by hundreds of R packages and is among the top 1% of most downloaded packages. It is designed to unify and leverage common parallelization frameworks in R and to make new and existing R code faster with minimal efforts of the developer. The futureverse allows you, the developer, to stay with your favorite programming style, and end-users are free to choose the parallel backend to use (e.g., on a local machine, across multiple machines, in the cloud, or on a high-performance computing (HPC) cluster).”

I want to send out a big thank you to useR! organizers, staff, and volunteers, and everyone else who contributed to this event.


To leave a comment for the author, please follow the link and comment on their blog: JottR on R. offers daily e-mail updates about R news and tutorials about learning R and many other topics. Click here if you're looking to post or find an R/data-science job.
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.

Never miss an update!
Subscribe to R-bloggers to receive
e-mails with the latest R posts.
(You will not see this message again.)

Click here to close (This popup will not appear again)