Job Launcher Changing where we run R stuff
summary
RStudio Job Launcher runs R work on external schedulers and Kubernetes clusters so heavy tasks move off the server. It supports ad-hoc jobs and containerized sessions via plugins (local, Kubernetes, Slurm preview). Example: generating 100 Twitter text portraits takes ~7 minutes on 2 CPU cores; moving workloads to a Kubernetes node fleet (nodes with 32 CPUs and 120 GB RAM) and requesting ~25 cores reduces multi‑hour jobs to minutes. Container images carry R versions and packages for reproducible, isolated sessions.
AI-written summary · about
chapters (12)
- 0:00Intro
- 3:38RStudio Job Launcher
- 5:05What are plugins
- 5:50What about other plugins
- 6:16Job types
- 7:20Dependencies
- 8:29Scaling
- 9:32Job Launcher
- 13:24Containerized Sessions
- 14:29Frequently Asked Questions
- 15:25Summary
- 16:02Questions
related talks
19mRemote Content Execution with RStudio Connect and Kubernetes
07mInterview of Ronald Dehuysser
21mScaling and automating R workflows with Kubernetes and Airflow
29mScale Your Batch / Big Data / AI Workloads Beyond the K8s...
25mScale your Batch / Big Data / AI Workloads Beyond the Kubernetes Scheduler
29mData Processing Efficiency: Optimizing Batch Workloads on Kubernetes With Custom Schedulers
29mAdapt to Unified and Pluggable Cluster Management Platform at LinkedIn
33mFrom spreadsheet scheduling to Kubernetes: building an on-premise ML platform