A ports freeze means that commits will be few and far between and only by approval.

bonnie 2.0.6 benchmarks =16

Performance Test of Filesystem I/O
Maintained by: se@FreeBSD.org
Port Added: unknown

---

---

Bonnie: Filesystem Benchmark Program

Bonnie tests the speed of file I/O using standard C library calls.
It does reads and writes of blocks, testing for the limit of sustained
data rate (usually limited by the drive or controller) and updates on
a file (better simulating normal operating conditions and quite dependent 
on drive and OS optimisations).

The per-character read and write tests are generally limited by CPU speed
only on current-generation hardware. It takes some 35 SPECint92 to read
or write a file at a rate of 1MB/s using getc() and putc().

The seek tests are dependent on the buffer cache size, since the fraction
of disk blocks that fits into the buffer cache will be found without any 
disk operation and will contribute zero seek time readings. I.e. if the 
buffer cache is 16MB and the Bonnie test file is 32MB in size, then the 
seek time will come out as half its real value. The seek time includes 
rotational delay, and will thus always come out higher than specified for 
a drive.

WWW: http://www.textuality.com/bonnie/

CVSWeb : Sources : Main Web Site : Distfiles Availability : PortsMon

---

To install the port: cd /usr/ports/benchmarks/bonnie/ && make install clean
To add the package: pkg_add -r bonnie

---

Configuration Options

     No options to configure

---

Master Sites:

http://www.acnc.com/benchmarks/

http://www.textuality.com/bonnie/

ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/

- Remove the DESTDIR modifications from individual ports as we have a new,
  fully chrooted DESTDIR, which does not need such any more.

Sponsored by:   Google Summer of Code 2007
Approved by:    portmgr (pav)

Install to /... instead of to /...

Fix two bugs affecting bonnie runs with large data files:

- A printf format specified a long operand but received an offset_t value.

- The random numbers for large seek ranges were computed without regard
  for operator precedence and could become negative (for file sizes larger
  than 4GB, which was a wrong test for "large", since it did not account
  for the chunk size).

The problems were found by etc at fluffles dot net (Enlightenment). Thanks
for the detailed report. Guess there aren't many Bonnie users with multi-
terabyte RAID systems; these bugs had been found long ago, else ...

SHA256ify

Approved by:    krion@

Add SIZE data to distinfo files.

Submitted by:   trevor

Use PLIST_FILES (bento-tested, marcus-reviewed).

Clear moonlight beckons.
Requiem mors pacem pkg-comment,
And be calm ports tree.

E Nomini Patri, E Fili, E Spiritu Sancti.

Use 8k chunks as Bonnie 1.0 did rather than 16k ones.
Otherwise the benchmark output is different (and noticeably lower) when
compared to 1.0.

Requested by:   se

Upgrade to version 2.0.6.

Reviewed by:    se

It is easier to modify the manpage if it is a normal text rather than a patch.

It is easier to modify the manpage if it is a normal text rather than a patch.

Massive style enforcement - use ^I instead of spaces for variables identation.  
 

Convert category benchmarks to new layout.  

12 vulnerabilities affecting 34 ports have been reported in the past 14 days

^* - modified, not new

All vulnerabilities