Pepitedata
  • Home
  • Audits
  • Expert Call
  • About
  • Blog
  • Contact

LOSF

A penguin overwhelmed by an avalanche of tiny blue small files spilling out of index drawers and overflowing a bucket, illustrating MinIO under a lots-of-small-files workload
MinIO

MinIO and Lots of Small Files: Why It’s Not a Database, and Why That Matters

MinIO was not built for Lots of Small Files (LOSF). No global index, no read repair, and a scanner that can take weeks to notice silent corruption. Here is what breaks, why tiering makes it worse, and when you should use a database instead.

By jlu, 2 weeks2026-06-29 ago
Diagram: MinIO erasure-coding storage inflation on small objects — per-drive xl.meta metadata replicated across the erasure set
data

Stop using MinIO as a NoSQL database — why S3 object stores collapse on small-file workloads

Two MinIO platforms, same root cause: used as a NoSQL store. Field notes on LIST IOPS, XFS directory limits, scanner & heal SLAs, the erasure-coding storage-efficiency inversion on small objects, and why Apache Cassandra (or Ceph) is the right answer on-prem in 2026.

By jlu, 2 months2026-05-17 ago
  • Privacy Policy
  • Mentions légales
  • CGV
  • Cookies
Hestia | Developed by ThemeIsle