Commit Graph

61 Commits

Author SHA1 Message Date
Kelly Lucas
1274c14753 Merge pull request #30 from mbrukman/readme-html-to-markdown
Fixed Markdown formatting.
2015-12-22 08:56:40 -08:00
Misha Brukman
06a50c0f27 Fixed Markdown formatting.
* Removed HTML tags, replacing with Markdown as appropriate
* Fixed spelling, grammar, etc.
* Added missing code formatting
2015-12-21 19:14:15 -08:00
Kelly Lucas
654b2d2810 Merge pull request #29 from mbrukman/license
Added the GPL v2 license file.
2015-12-18 20:14:02 -08:00
Misha Brukman
599754f79d Added the GPL v2 license file.
The original source of this repo is https://code.google.com/p/byte-unixbench/
where the project is listed as being released under the GPL v2 license, but
as it was metadata in Google Code but not explicitly named in the project source
code itself, it did not transfer when the project was moved to GitHub.

This change clarifies the license of the project and provides a complete copy of
the license to make it explicit to future users and contributors.
2015-12-17 22:09:44 -08:00
Steven Noonan
910276909b make maxCopies unbounded for 'system' and 'misc' suites
Quoting original author of this patch:

Simply un-limits the 'misc' and 'system' suites.

Half-related thoughts about testing quality:

I'm curious why there's a shell1, shell8, and shell16 set of tests. Aren't the
latter two equivalent to './Run -c 8 shell1' and './Run -c 16 shell1'? I think
shell8 and shell16 are pointless if this is the case.

At the very least, I think shell8 should be out of the default run (the $index
set), because it will essentially give a misleading number if you have more
than a single core in the system. Isn't the purpose of the serial run to
essentially measure how well the system performs on single-threaded activities?
Or perhaps to measure how well a single core performs? Having 'shell8' in the
$index set artificially inflates the score for serialized runs and artificially
damages the score during maxed-out parallelized runs. If you are actually
interested in seeing how well 'shell8' does on exactly one core, shouldn't you
do the equivalent of 'taskset 1' on it, forcing the child processes to stay on
that single core?

End of quote.

Signed-off-by: Carlos L. Torres <carlos.torres@rackspace.com>
2015-06-06 17:40:32 -05:00
Anthony Voellm aka Tony the P3rfguy
c5cb9f2dd6 Update README.md 2015-06-04 10:31:37 -07:00
Anthony Voellm aka Tony the P3rfguy
c7ea5d492b Update README.md 2015-06-04 10:20:18 -07:00
kdlucas
82e5e92991 Create README.md 2015-05-07 10:37:42 -07:00
kdlucas@gmail.com
9e74ce4889 Updated logo file to reflect version change to 5.1.3 2011-01-18 06:48:59 +00:00
kdlucas
7df8999264 Rev'd to 5.1.3 to add fix for parallel job compilation. 2011-01-14 17:30:40 +00:00
headstay
f53eadaa3e Version 5.1.2. 2009-10-28 01:52:39 +00:00