borg-benchmark-crud(1)

💅 borg-benchmark-crud — the manual page, bestie edition

okay so you're reading the man page for borg-benchmark-crud(1), part of the borg backup tool. buckle up, it's giving ✨performance metrics✨

---

🌸 NAME 🌸

borg-benchmark-crud — Benchmark Create, Read, Update, Delete for archives.

like… it literally does what it says on the tin, no cap.

---

✨ SYNOPSIS ✨

borg [common options] benchmark crud [options] REPOSITORY PATH

---

💖 DESCRIPTION 💖

so this command benchmarks borg CRUD (create, read, update, delete) operations. that's the whole vibe. 🦋

It creates input data below the given PATH and backs up this data into the given REPO. The REPO must already exist — it could be a fresh empty repo or an existing repo, doesn't matter, the command will create / read / update / delete some archives named borg-benchmark-crud* there.

bestie, make sure you have free space there, you'll need about 1GB each (+ overhead). no pressure but like… actually pressure 💀

If your repository is encrypted and borg needs a passphrase to unlock the key, use:

BORG_PASSPHRASE=mysecret borg benchmark crud REPO PATH

Measurements are done with different input file sizes and counts. The file contents are very artificial (either all zero or all random), so the measurement results do not necessarily reflect performance with real data. Also, due to the kind of content used, no compression is used in these benchmarks. 🎀

• C- == borg create (1st archive creation, no compression, do not use files cache)
  • C-Z- == all-zero files. full deduplication; this primarily measures reader/chunker/hasher.
  • C-R- == random files. no deduplication, measuring throughput through all processing stages.
• R- == borg extract (extract archive, dry-run, do everything, but do not write files to disk)
  • R-Z- == all-zero files. Measuring heavily duplicated files.
  • R-R- == random files. No duplication here, measuring throughput through all processing stages, except writing to disk.
• U- == borg create (2nd archive creation of unchanged input files, measure files cache speed)
  • The throughput value is kind of virtual here, it does not actually read the file.
  • U-Z- == needs to check the two all-zero chunks' existence in the repo.
  • U-R- == needs to check existence of a lot of different chunks in the repo.
• D- == borg delete archive (delete last remaining archive, measure deletion + compaction)
  • D-Z- == few chunks to delete / few segments to compact/remove.
  • D-R- == many chunks to delete / many segments to compact/remove.

ngl there might be quite some variance in these measurements. Try multiple measurements and have an otherwise idle machine (and network, if you use it). like, close your 47 browser tabs first, i'm begging 🙈

---

🌈 OPTIONS 🌈

See borg-common(1) for common options of Borg commands. iykyk 🫶

💜 arguments

• REPOSITORY — repository to use for benchmark (must exist)
• PATH — path where to create benchmark input data

---

👑 SEE ALSO 👑

borg-common(1)

---

🌟 Author 🌟

The Borg Collective

---

and that's the whole page, you ate that 💅✨

this was borg-benchmark-crud(1) from the borg backup tool, dated 2026-07-18 — periodt, go benchmark something bestie 🎀🦋