Site icon R-bloggers

GPU Support in Bioconductor

[This article was first published on Bioconductor community blog, 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.
< section id="introduction" class="level1">

Introduction

GPU acceleration enables faster and more scalable analysis workflows, especially for tasks like deep learning, image processing, and large-scale genomics, making Bioconductor more powerful for researchers working with complex data. Thanks to funding from CZI EOSS 6, Bioconductor is developing better support for maintainers authoring GPU-capable packages, including adding a new Nvidia GPU build machine maintained at the University of Padova, new release and devel (Nvidia) GPU software builds, GPU-aware containers, and a biocViews GPU term. This post shares these new resources and how Bioconductor package maintainers can take advantage of them.

< section id="gpu-support" class="level2">

GPU Support

3.22 GPU Software report

The BBS GPU Software reports are available at

Looking at the reports, you’ll notice three new build nodes:

The Nvidia CUDA compiler driver and the Nvidia System Management Interface for each machine appears at the bottom of their node info reports. Both amarone and kakapo1 use a BBS-like container based on Nvidia’s CUDA container available to maintainers.

Additionally, a biocViews term GPU has been added.

< section id="how-to-take-advantage-of-new-gpu-support" class="level2">

How to take advantage of new GPU support

< section id="help-users-find-your-gpu-capable-package" class="level3">

Help users find your GPU-capable package

Add GPU as a biocView term for your package.

< section id="opt-in-to-the-bbs-gpu-software-builds" class="level3">

Opt in to the BBS GPU Software builds

The GPU Software builds, like the Long Tests builds, require a .BBSoptions file at the top level of a package repository with a GPU_reliance setting.

< section id="gpu-optional-packages" class="level4">

GPU-optional packages

If a package supports GPU if available, maintainers can opt in to the GPU software build by setting GPU_reliance to optional:

GPU_reliance: optional

Make sure you have tests that utilize GPUs if available.

< section id="gpu-required-packages" class="level4">

GPU-required packages

Maintainers creating packages requiring GPUs in order for the package to be build should set GPU_reliance to required:

GPU_reliance: required

See Advanced Build Options for information.

< section id="future-work" class="level3">

Future work

More work is being done to understand how we can make the best use of GPUs within Bioconductor by developing a package to understand GPU usage and propose best practices, but we also need a better understanding of what packages are using GPUs and what our community needs. Learn more about the project at https://waldronlab.io/czieoss6-biocgpu/.

© 2025 Bioconductor. Content is published under Creative Commons CC-BY-4.0 License for the text and BSD 3-Clause License for any code. | R-Bloggers

To leave a comment for the author, please follow the link and comment on their blog: Bioconductor community blog.

R-bloggers.com 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.
Exit mobile version