working-with-large-data

Process terabyte-scale datasets out-of-core with Parquet, DuckDB, Polars, and Arrow.

5|1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/yale-som-hpc/claude-code-marketplace --skill working-with-large-data
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: working-with-large-data
Source: https://github.com/yale-som-hpc/claude-code-marketplace/tree/main/plugins/hpc/skills/working-with-large-data
Command: npx skills add https://github.com/yale-som-hpc/claude-code-marketplace --skill working-with-large-data

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Process data too large to fit in memory on the Yale SOM HPC cluster by using columnar formats, lazy evaluation, and on-disk processing with Parquet, DuckDB, Polars, and Arrow.

Core Features & Use Cases

  • Out-of-core processing: operate on datasets larger than RAM by streaming and chunking.
  • Format-agnostic pipelines: leverage Parquet, Arrow, and DuckDB for efficient data workflows.
  • Scalable HPC workflows: integrate with Slurm-backed clusters to run chunked data pipelines.

Quick Start

Launch a Slurm job to read Parquet data and process it efficiently with DuckDB or Polars in chunked steps.

Frequently Asked Questions about working-with-large-data

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I process Parquet datasets larger than memory on an HPC cluster?

To process Parquet datasets larger than memory on an HPC cluster, use out-of-core processing with DuckDB or Polars to stream and chunk data. This prevents RAM exhaustion by leveraging lazy evaluation and on-disk operations.

What is out-of-core processing and when do I need it for large data workflows?

Out-of-core processing handles large data by streaming and chunking datasets that exceed available RAM. You need it for terabyte-scale workflows where loading entire datasets into memory would cause system failure or crashes.

Does DuckDB work with Polars for chunked data processing on Slurm?

Yes, DuckDB works with Polars for chunked data processing on Slurm by utilizing columnar formats and Arrow integration. They enable scalable HPC workflows through lazy evaluation and on-disk operations to manage memory usage.

What's the best way to run batch data pipelines on Yale SOM HPC without hitting memory limits?

The best way to run batch data pipelines on Yale SOM HPC without hitting memory limits is launching Slurm jobs that read Parquet data and process it in chunked steps using DuckDB or Polars, applying lazy evaluation.

Why does loading large Arrow datasets exhaust RAM and how can I prevent it?

Loading large Arrow datasets exhausts RAM because eager loading pulls entire datasets into memory. Prevent this by applying out-of-core processing with Polars or DuckDB, using lazy evaluation and chunked streaming.