Skip to content

Releases: cunnie/gobonniego

`-seconds` flag sets duration (timer)

12 Apr 14:22
Compare
Choose a tag to compare

Able to set the benchmark to run for an entire day in order to exhaust AWS's I/O Credits and determine what performance can be expected from gp2 storage.

-runs is not suitable for this task — for fast storage it finishes too quickly, for slow storage, too slowly.

JSON: timestamps & seconds, aggressive buffer cache purging

08 Apr 15:51
Compare
Choose a tag to compare

The JSON output for duration is now in seconds not nanoseconds. Nanoseconds was a poor choice.

The JSON output includes timestamps, both of when the command was invoked and for each individual run (an individual run consisting of a write test, a read test, and an IOPS test).

When run as root on Linux or macOS, flushes buffer cache every 3 seconds.

Don't panic() if GoBonnieGo directory already exists

21 Mar 13:12
Compare
Choose a tag to compare

It may seem silly to generate a release to fix a minor bug, but it was blocking the building of a new BOSH release which included a mechanism to clear the buffer cache, which was quite important.

Clear buffer cache on macOS and Linux

20 Mar 01:19
Compare
Choose a tag to compare

When run as root, clears buffer cache on macOS and Linux, which makes for more accurate IOPS.

It clears the buffer cache before the read test and the IOPS test.

1.0.5 new flags: `-json`, `-runs`, `-iops-duration`

10 Mar 20:54
Compare
Choose a tag to compare

We've added JSON output as an option (-json).

We've also added the ability to specify N runs (e.g. -runs 5). This is useful for gathering a large dataset.

And finally, for rapid testing, we added the -iops-duration flag. Sometimes the fifteen-second default is too long: -iops-duration 0.5

1.0.4 MB *and* MiB

25 Feb 01:27
Compare
Choose a tag to compare

The big change is that the -v option reports in both MB and MiB. This is to avoid confusion when manually calculating the throughput.

Under the hood, The package bench will not panic(), only return an error. It's a better-behaved package as a result.

1.0.3 splash message, MB/s, not MiB/s

19 Feb 20:21
Compare
Choose a tag to compare

Most of the changes of this release were under-the-hood: gobonniego underwent a grand refactor where much of the code was pulled out of package main and moved into a new package, bench

Also we added a splash message — we found that first time users were thrown off by not seeing any output for the first few seconds when invoking gobonniego. The splash message is a form of reassurance ("don't worry, we're doing something).

The results are now displayed in MB/s not MiB/s. This is to make gobonniego conform to industry norms.

1.0.2 FreeBSD + `-size`

17 Feb 18:03
Compare
Choose a tag to compare

Added FreeBSD suport

-size parameter enables the specification of the data set size (for large RAM systems & quick testing)

1.0.1

15 Feb 21:00
Compare
Choose a tag to compare

Rename executable to gobonniego, previously was bonniego.

Per Tim Bray's suggestion:

maybe "GoBonnieGo"?

1.0.0

14 Feb 18:55
Compare
Choose a tag to compare

bonniego produces three metrics: read, write, and IOPS.