# Easy CPU/GPU Arrays and DataFrames — Run your Dask code where you’d like

**URL:** <https://openplanetary.discourse.group/t/easy-cpu-gpu-arrays-and-dataframes-run-your-dask-code-where-you-d-like/619>\
**Category:** Python\
**Created:** [April 16, 2023, 2:11am UTC](https://openplanetary.discourse.group/t/easy-cpu-gpu-arrays-and-dataframes-run-your-dask-code-where-you-d-like/619 "2023-04-16T02:11:11Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![cmarmo](https://yyz2.discourse-cdn.com/free1/user_avatar/openplanetary.discourse.group/cmarmo/32/271_2.png) [@cmarmo](https://openplanetary.discourse.group/u/cmarmo)\
**Post date:** [April 16, 2023, 2:11am UTC](https://openplanetary.discourse.group/t/easy-cpu-gpu-arrays-and-dataframes-run-your-dask-code-where-you-d-like/619/1 "2023-04-16T02:11:11Z")

</div>

> **[Easy CPU/GPU Arrays and DataFrames — Run your Dask code where you’d like](https://dask.discourse.group/t/easy-cpu-gpu-arrays-and-dataframes-run-your-dask-code-where-you-d-like/1757)**
>
> Summary As of Dask 2022.10.0, users can optionally select the backend engine for input IO and data creation. In the short-term, the goal of the backend-configuration system is to enable Dask users to write code that will run on both CPU and GPU...