Free while we’re in preview

Get DriveForge

Benchmark several drives against each other, same settings for every one.

The Mac button is for Apple Silicon. On an older Intel Mac, get this one instead.

One file, both ways. Double-click it for the window. Run the same file from a command prompt with arguments and it behaves as the command-line tool, because the engine is inside it. Nothing else to download and nothing to keep beside it.

Early preview. The window has been built and run, but not yet on a real Windows PC or Mac, so expect rough edges. The engine underneath it is fully tested.

One file — no installer
Runs on your machine, offline
Source code published below

Free while in preview. It isn’t signed yet, so Windows or macOS will ask you to confirm the first time you open it. At launch, DriveForge is included in every plan along with the rest of the range.

Where should the write-heavy job live?

You have an SSD and a spinning disk mounted, or a NAS share next to a local folder. driveforge bench /mnt/ssd /mnt/hdd --size 512MB writes a temp file into each, fsyncs it, times that, reads it back, times that too, and prints a table ranked fastest write first. Every target gets identical --size and --block, which is the only thing that makes the ranking mean anything. A directory that can’t be written is marked FAILED with a reason and dropped from the ranking while the rest still run.

Read this before quoting a number

It measures file-API throughput through your OS and filesystem, sequentially, on one thread. Not raw block-device speed, not random I/O. Small sizes get flattered by the page cache, badly so when both targets sit on the same underlying disk, so use a few hundred MB at minimum.

Partitioning, cloning and SMART all need privileged raw-device access, so they’re not in this build.

Reading on the job itself

How to tell whether a drive is failing Back it up first, then measure. A drive that reads at full speed for most blocks and stalls for hundreds of...

The rest of Disk Operations Suite

The disk itself: how fast it reads and writes, whether its partition table agrees with itself, and where the surface is struggling.

DiskOps

Simple Ready

Writes 256 MB, fsyncs it, reads it back. Two numbers in MB/s.

PartitionGuard

Vertical Ready

Reads a disk image's partition table and checks whether it contradicts itself.

SectorPilot

Team Ready

Times every block of a disk image and maps which ones are struggling.

Advanced & technical details Command-line builds, source code, checksums and a recorded session — for developers and IT teams

A working CLI prototype of the multi-target comparison engine: benchmark several directories in one invocation with a genuinely apples-to-apples size/block per target, ranked by write throughput, with per-target failures isolated so one bad path can't abort the whole comparison. A raw block-device mode is still on the roadmap.

Naming status

Working name only — brand verdict **AVOID** (Very High). Collision: DriveForge. Rename completely.

What it draws on

Existing paid software whose best ideas shaped this program: EaseUS Partition Master Professional, AOMEI Partition Assistant Professional, DiskGenius Professional, Hard Disk Sentinel Professional.

Command line

There is nothing extra to install. The program you download is the command-line tool as well: give it arguments instead of double-clicking it and it runs as one, with its output on your terminal. The standalone builds below are the same engine on its own, for machines where you would rather not ship a window at all.

DriveForge - multi-target disk I/O throughput comparison (prototype)

Usage:
  driveforge bench <dir1> [<dir2> ...] [--size 256MB] [--block 1MB] [--json]
  driveforge help

Commands:
  bench    Run the same sequential write/read throughput benchmark against
           each target directory, independently, and print a ranked
           comparison sorted by write MB/s (fastest first).

Flags for bench:
  --size    Total bytes to write/read per target, e.g. 256MB, 1GiB, 512KB
            (default 256MB). Applied identically to every target.
  --block   Chunk size for each write/read call, e.g. 1MB, 256KB
            (default 1MB). Applied identically to every target.
  --json    Emit a JSON report instead of human-readable text

Notes:
  - Same methodology as DiskOps (sequential, single-threaded, file-API
    throughput - not a raw block-device benchmark) run across multiple
    targets in one pass for an apples-to-apples comparison.
  - A target that doesn't exist or isn't writable is reported as FAILED with
    a reason; the other targets still run and are ranked normally.
  - OS and filesystem caching mean small --size values can report
    unrealistic numbers, especially if targets share the same underlying
    filesystem/cache. Use at least a few hundred MB for a meaningful result.

Examples:
  driveforge bench /mnt/ssd /mnt/hdd --size 512MB
  driveforge bench . /tmp /mnt/data --size 1GiB --block 4MB --json

Recorded from the shipped binary, not written by hand.

Windows (amd64) macOS (Apple Silicon) macOS (Intel) Linux (amd64)

Source

Every file the program is built from:

console.go · console_test.go · guided.go · main.go

SHA-256 checksums · build instructions & scope notes · full build plan

DriveForge

Preview