IOMELT(1)

📦 version 0.7, in nixos 26.05, nixpkgs unstable

💅 IOMELT(1) — the iomelt page, bestie edition 💅

okay so this is iomelt, and it lives in the User Manuals section of your manual pages, and I am literally about to make you love a storage benchmark. yes, a benchmark. stay with me. 🫶

✨ NAME ✨

iomelt — a simple yet effective IO benchmark tool 🌸

🦋 SYNOPSIS 🦋

iomelt [-dDhnoOrRv] [-b BYTES ] [-s BYTES ] [-p PATH ]

💖 DESCRIPTION 💖

okay so iomelt is a benchmark tool for storage devices, and honestly? it's giving main character energy for something so understated. it's designed to be simple to use and to produce consistent and reproducible results — no chaos, no drama, just numbers you can trust. ✨

by default it creates a 10 Megabytes file using the optimal block size as returned by statvfs(), and then it runs a series of five different tests: serial write, serial read, random rewrite, random read, mixed read/write. five tests, five vibes, all in one go. 💅

🎀 OPTIONS 🎀

  • -d — dump data in a format that can be easily digested by pattern processing commands like awk. machine-readable, bestie. 🤖
  • -D — print time in seconds since epoch. raw timestamp realness. ⏱️
  • -h — prints usage parameters. the "help me help you" flag. 🙈
  • -H — omit header row when dumping data. bye bye header, you will not be missed. 👋
  • -n — do not convert bytes to a human readable format. keep those raw numbers raw. 🔢
  • -o — do NOT display results (does not override -d). yes, a benchmark that shows you nothing. iconic honestly. 💀
  • -O — reopen workload file between tests. fresh file, fresh start, fresh vibes. 🦋
  • -r — creates a random suffix to the test file (useful when testing clustered distributed file systems that use file name as a hash key). so specific, so valid. 🎲
  • -R — tries to minimize cache effects by using Direct IO. heads up though: the underlying file system must support the O_DIRECT open() flag. the aligned buffer is created using posix_memalign(). no cap, this one's doing the most. 🔥
  • -v — controls the level of verbosity. 🗣️
  • -vv — even more verbose output. it's giving extra. 💬💬
  • -V — displays version number. 🌈
  • -b BYTES — block size used for read and write operations. please note that unless specified, iomelt will try to use the optimal block size as returned by statvfs(). block size must be a power of two. ⚡
  • -s BYTES — test file size. K, M, G may be used as suffixes for Kilobytes, Megabytes and Gigabytes, respectively. pick your unit, live your truth. 🍓
  • -p PATH — complete path to the directory where the test file should be created. 📁

👑 AUTHOR 👑

Written by Rodrigo Campos (camposr@gmail.com) — absolute legend, we stan. 💜

🔗 SEE ALSO 🔗

open(2), statvfs(3), posix_memalign(3), posix_fadvise(2), read(2), write(2) — the whole friend group, fr fr. 🫶

Detailed documentation and latest version may be obtained at http://iomelt.com ⭐

💀 BUGS 💀

okay so there are two things you need to know, and I'm saying this with love. 🙈
  • The -v option must precede the -p option in order to display the debugging information for the chdir() operation. order matters, bestie. 😭
  • The unit conversion function will fail for large file sizes in 32 bit systems due to integer overflows. not a vibe, but forewarned is forearmed. ⚠️

and that's the whole page, no skips, no shortcuts. 💅 this one came from Linux, dated AUGUST 2012, and it's IOMELT(1) all the way down — mwah, go benchmark something. 💖✨🎀

📦 where this page comes from