You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We now use unified memory + prefetching by default for cuDF Pandas, which has materially improved the user experience while still providing large speedups to workflows -- particularly on the lower-memory GPUs where users are frequently trying to process e.g., 5-20GB datasets.
In contrast, users of the Polars GPU engine are currently at high risk of experiencing out-of-memory errors when processing the medium-sized datasets for which they're hoping accelerated computing can help them handle.
A brief series of ad-hoc investigations exploring UVM for Polars on PDS-H on 100-200GB datasets on higher-memory GPUs like the A100 and H100 have showed promise but run into some performance challenges in selected scenarios. We should formalize this investigation to target enabling UVM for the Polars GPU engine.
The text was updated successfully, but these errors were encountered:
We now use unified memory + prefetching by default for cuDF Pandas, which has materially improved the user experience while still providing large speedups to workflows -- particularly on the lower-memory GPUs where users are frequently trying to process e.g., 5-20GB datasets.
In contrast, users of the Polars GPU engine are currently at high risk of experiencing out-of-memory errors when processing the medium-sized datasets for which they're hoping accelerated computing can help them handle.
A brief series of ad-hoc investigations exploring UVM for Polars on PDS-H on 100-200GB datasets on higher-memory GPUs like the A100 and H100 have showed promise but run into some performance challenges in selected scenarios. We should formalize this investigation to target enabling UVM for the Polars GPU engine.
The text was updated successfully, but these errors were encountered: