fio vs y-cruncher

fio is a free storage I/O workload simulator for performance testing and reproducing bugs. Its job files can define multiple threads, processes and files, with sequential, random or mixed reads and writes using buffered, direct or raw I/O. Tune block and I/O size, I/O engine, queue depth, target files or devices, and job count. Documented engines include Linux io_uring and libaio, POSIX asynchronous I/O, and synchronous read/write options. Separate engines support HTTP GET and PUT requests to WebDAV or S3 endpoints and access to Ceph RADOS and RBD. Verification options can check written data after a workload, including repeated burn-in tests. Results are available in normal text, terse, JSON and JSON+ formats, plus bandwidth and latency logs; terse output is intended for scripts, tables or graphs. fio supports Linux, Solaris, AIX, HP-UX, macOS, NetBSD, OpenBSD, Windows, FreeBSD and DragonFly. The HTTP engine supports direct I/O only at depth 1, with scaling through multiple jobs.

y-cruncher calculates Pi and other mathematical constants to trillions of digits, and also serves as a multithreaded benchmark and stress-testing program for overclockers and hardware enthusiasts. For most constants, it uses separate algorithms to compute and verify results. Its multithreading uses modern multi-core processors without significantly increasing memory usage, and it supports SIMD instruction sets such as SSE, AVX and AVX512. For computations that exceed available memory, y-cruncher manages swap space and can use multiple drives for disk swapping. It can detect and correct minor errors attributed to hardware instability or software bugs. Windows and Linux downloads are available; the listed requirements are Windows 8 or later, 64-bit Linux, and an x86 or x64 processor. The Linux static build lacks TBB and NUMA binding, while the dynamic build supports all features but is less portable. The free plan permits non-commercial and academic use; commercial-purpose licensing may be available by contacting the developer. Major algorithm redesigns and rewrites are on hiatus, though maintenance and some processor optimizations continue.