macOS

Disk Analyzer para sa mga data scientist

Datasets, conda environments, model checkpoints, and notebooks with embedded outputs. Data work fills disks with files that all look important — until you measure them.

Where the gigabytes hide

01

Checkpoint mountains

Every training run keeps 'just one more' checkpoint. Times hundreds.

02

Env sprawl

Conda and venv environments duplicate gigabytes per project.

03

Output-embedded notebooks

A 200 MB .ipynb is 199 MB of base64 plots.

The workflow

STEP 01

Rank by size, filter by age

Oldest-plus-largest is the delete shortlist. Statistics views help here.

STEP 02

Quarantine checkpoints

Keep the best per experiment; the collector holds the rest for a final review.

STEP 03

Strip notebook outputs

Re-run beats storage. Clear outputs before archiving notebooks.

STEP 04

Measure envs before pruning

Allocated size can surprise — verify before removing environments.

Tools worth installing

NullDisk first — native map, staged collector, zero telemetry. Then, depending on taste:

Mga madalas itanong

Which view helps with datasets?

Age-plus-size statistics (JDiskReport's specialty) or a treemap sorted by size. Numbers beat vibes for data hoards.

Are data files safe to delete?

Derived artifacts (checkpoints, caches, outputs) yes; raw data almost never. When in doubt, archive to external storage first.