microperceptrnNVIDIA Inception Program member
All benchmarks

Storage

NVMe raw read

Lenovo Yoga 7 2-in-1 16ILL10 · Core Ultra 5 226V · 16 GB

One captured run per system

The 64 GiB partition Cosmos keeps model packs on, on the Lenovo Yoga 7 2-in-1's SSD, read 7 ways: runs of 64 MiB to 1 GiB scattered over 8–64 GiB, and one sequential pass. 5 of them land within 1% of 6.0 GB/s — the drive's own limit, below the PCIe 4.0 ×4 link's 7.9 GB/s raw rate. Each system reads through its fastest path: Kore's pack engine, and fio with io_uring, direct I/O and registered buffers.

Laptop
Lenovo Yoga 7 2-in-1 16ILL10
CPU
Intel Core Ultra 5 226V
GPU
Intel Arc 130V · Xe2 (integrated)
Memory
16 GB, shared by CPU, GPU and NPU
Storage
SK hynix HFS512GEM4X182N · PCIe 4.0 ×4 NVMe
NVMe raw read in GB/s, per case: Cosmos, Ubuntu + fio, and the change over Ubuntu + fio
PatternCosmosUbuntu + fioΔ
Random64 MiB / 64 GiB5.785.559+4.0%
Random1,024 MiB / 64 GiB6.015.916+1.6%
SequentialContiguous · see note6.025.313+13.3%
Random64 MiB / 8 GiB5.645.027+12.2%
Random256 MiB / 16 GiB5.955.177+14.9%
Random256 MiB / 64 GiB5.995.396+11.0%
Random512 MiB / 64 GiB6.005.387+11.4%

GB/s, decimal · group / span

Group = one contiguous read run, not the device I/O size. 12 GiB per case; the last case reads 18 GiB.

Sequential layouts differ: Kore declares one 64 GiB span; fio reads eight adjacent 1.5 GiB regions, one per job.

What each system ran

Software
CosmosKore pack engine (pack bench)
Ubuntu + fioUbuntu 26.04.1 LTS · Linux 7.0.0-38 · fio 3.41
Submission
Cosmos4 NVMe rings, round robin
Ubuntu + fioio_uring · 8 jobs × queue depth 16
Transfer size
Cosmos256 KiB — the controller's maximum transfer
Ubuntu + fio128 KiB — the kernel's max_sectors_kb for this drive
Buffers
CosmosFunded and IOMMU-mapped before timing
Ubuntu + fioO_DIRECT · fixed buffers · registered file
Commands for every case

fio, shared by every case

sudo fio --name=pack --filename=/dev/nvme0n1p6 --readonly --direct=1 --ioengine=io_uring --fixedbufs=1 --registerfiles=1 --thread --numjobs=8 --group_reporting --bs=128k --iodepth=16 --invalidate=0 --norandommap --randrepeat=0
  1. 64 MiB runs over 64 GiBkore › pack bench 4 64 3fio … --rw=randread:512 --ba=64M --size=64G --io_size=1536M
  2. 1,024 MiB runs over 64 GiBkore › pack bench 4 1024 3fio … --rw=randread:8192 --ba=1024M --size=64G --io_size=1536M
  3. Sequentialkore › pack bench 4 64 3 seqfio … --rw=read --size=1536M --offset_increment=1536M
  4. 64 MiB runs over 8 GiBkore › pack bench 4 64 3 span 8fio … --rw=randread:512 --ba=64M --size=8G --io_size=1536M
  5. 256 MiB runs over 16 GiBkore › pack bench 4 256 3 span 16fio … --rw=randread:2048 --ba=256M --size=16G --io_size=1536M
  6. 256 MiB runs over 64 GiBkore › pack bench 4 256 3 span 64fio … --rw=randread:2048 --ba=256M --size=64G --io_size=1536M
  7. 512 MiB runs over 64 GiBkore › pack bench 6 512 3 span 64fio … --rw=randread:4096 --ba=512M --size=64G --io_size=2304M

Evidence

Benchmark capture card, NVMe raw read throughput on the Core Ultra 5 226V laptop, Cosmos. A Kore terminal running pack bench, with the sequential run, 12288 MiB in 2136 ms: 6.02 GB/s, highlighted. The card reads 6.02 GB/s with 4 NVMe rings and a 256 KiB maximum transfer.(open full size)
Cosmos · 6.02 GB/sLenovo Yoga 7 2-in-1 16ILL10 · Core Ultra 5 226V · 16 GB
Benchmark capture card, NVMe raw read throughput, Ubuntu with io_uring. A terminal running fio 3.41 against the same partition, with the sequential result BW=5067MiB/s (5313MB/s)(12.0GiB/2425msec) highlighted. The card reads 5.313 GB/s with 128 KiB I/O and 8 jobs at depth 16.(open full size)
Ubuntu + fio · 5.313 GB/sLenovo Yoga 7 2-in-1 16ILL10 · Core Ultra 5 226V · 16 GB
A Kore terminal running pack info and seven pack bench commands against the 64 GiB pack partition, each reporting between 5.64 and 6.02 GB/s. The engine line reads round robin, 4 rings, 62021 submitted, 62021 completed, 0 in flight.(open full size)
pack benchLenovo Yoga 7 2-in-1 16ILL10 · Core Ultra 5 226V · 16 GB

The raw terminal behind the storage results: seven pack bench runs over the 64 GiB pack partition.

How it was measured

Same machine
Every comparison ran on one laptop, with the same silicon, drive and model weights on each side. On metal, Cosmos and Ubuntu were booted in turn; a result that ran Cosmos as a guest says how the guest was set up.
Current baseline
Ubuntu 26.04.1 LTS on Linux 7.0.0-38 with the latest Intel Xe drivers, on both machines; llama.cpp 0.8, with native NVFP4 and expert-cache support; fio 3.41 with io_uring, direct I/O and registered buffers, as the storage result's commands show. Current releases, not old builds, with one exception: the 27B result's llama.cpp run used an earlier build whose version wasn't recorded, and its settings say so.
Captured runs
Each figure is one captured run, read off its screenshot — not an average of repeated runs.
Native harnesses
Each system is measured with its own tools: Cosmos's chat and pack bench; llama.cpp's web UI and fio on Ubuntu. Transfer sizes and scheduling are reported, not equalized.
Units
Storage in decimal GB/s (10⁹ bytes per second). Tokens per second as each runtime reports its own generation speed.
Setup excluded
Buffer allocation and registration happen before timing on both systems; Cosmos prints its setup time on a separate line.

More results

Download Cosmos