Docs

What CLIO Core does for you.

CLIO Core is a runtime of storage, memory and compute modules that you compose into the I/O path a pipeline needs. It places data across RAM, NVMe, disk, GPUs and cloud buckets, and exposes it as a filesystem, a key-value store, paged memory or training data.

Written for
Scientists, HPC users and developers
Works on
Linux, macOS, Windows
License
BSD 3-Clause

The short version

You start one background process per node, the runtime, with a YAML file that lists the modules and storage tiers you want. What you put in front of them decides the product you get: Context FS mounts a directory that any program can use, the key-value store gives C++ and Python direct access to tags and blobs, memory expansion pages GPU and CPU arrays larger than memory, and clio-ml trains models on that data. The quickest way to see it work is the filesystem, so these docs start there.

Underneath every product, CLIO Core decides where each piece of data lives. Recently used data stays in RAM. Colder data moves to NVMe or disk. A persistent copy protects it across restarts. An index records the words in each file, so you can later ask "which files mention sea ice extent?" and get a ranked answer.

What you can do with it

The documentation, by technology

Each technology has its own documentation: what it is, how to install it, how to use it and its API.

The core concepts page explains tags, blobs, scores and pools in more depth. The design section covers the internals.

Where to start

  1. Install

    pip install iowarp-core works on most workstations. See Installation for conda, Docker, Spack and source builds.

  2. Mount and copy a file

    Follow Basic usage end to end.

  3. Shape your storage

    Use Compose local tiers when the defaults no longer fit.