AS SSD Benchmark vs Bonnie++
AS SSD Benchmark
alex-is.deBonnie++
github.comSide by side
| Figure | AS SSD Benchmark | Bonnie++ |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Windows | Yes | — |
| Linux | — | Yes |
| Self-hosted | — | Yes |
| Plans published | 1 | 1 |
| Spec score · Disk Benchmark Software | 7.8 (#10) | 8.4 (#3) |
| Spec score · PC Benchmark Software | 7.8 (#35) | 8.4 (#10) |
| Spec score · PC benchmark tools | 7.4 (#54) | 7.9 (#36) |
| Free plan | Yes | Yes |
| Purpose | AS SSD Benchmark measures the performance of solid state drives. | Bonnie++ benchmarks hard drives and file systems by measuring work per second and CPU usage. |
| Results | The program reports read, write, and overall performance scores, and can display measured values in MB/s or IOPS. | It can output results in CSV format, and companion tools convert CSV data to HTML or formatted plain text. |
Plans
In their own words
AS SSD Benchmark
AS SSD Benchmark has no write-up on Specifiction yet; its figures are above.
Bonnie++
Bonnie++ is a free, command-line benchmark suite for measuring filesystem and disk I/O performance on Linux. It exercises sequential input and output, rewrites, random seeks, and file operations including creation, stat, and deletion of many small files. The project describes these workloads as useful for investigating I/O bottlenecks in I/O-intensive applications, including database work, and for simulating file activity associated with Squid or INN. Bonnie++ can test more than 2 GB of storage on a 32-bit machine. Its -D option enables direct I/O for bulk tests, while -b calls fsync after each write and syncs the directory after file creation or deletion. Semaphore support can synchronize multiple instances. Results can be emitted as plain text or CSV, with companion tools to convert CSV into HTML or formatted plain text. The project is licensed under GPL version 2.0, and the repository includes source code and Debian, RPM, and Sun-related packaging files. Its documentation warns against running the benchmark on live production machines because it can affect services and consume disk space or inodes.