Commit Graph

14 Commits

Author SHA1 Message Date
Glenn Strauss
e477bc0341 prefer || over 'or' (portability w/ ancient Perl) 2022-02-24 02:24:57 -05:00
longerzone
d9242458ba A little trick to make Run recongnize the correct CPU cores on ARM machine, and then unixbench will run 1 threads and then multi-threads which is the correct process. Solve the Problem in issue : https://github.com/kdlucas/byte-unixbench/issues/60
github: closes #60
github: closes #61
2022-02-24 01:33:22 -05:00
Kelly Lucas
a62313ed54
Merge branch 'master' into environment_settings 2018-01-13 20:02:49 -08:00
t2-kob
fb25b1613f Added change directories and filename via Environment variables. 2018-01-12 11:53:53 +09:00
t2-kob
918ccbdf8b Added csv support(score only) by Environment variable. 2018-01-12 10:51:56 +09:00
Glenn Strauss
61663da4fd Run script fixes for AIX
github: closes #46
2017-06-29 20:19:39 -04:00
Glenn Strauss
c49ad96cae Run - detect num active CPUs
github: fixes #2, fixes #16
2016-09-18 00:37:45 -04:00
Glenn Strauss
a04d7c6b63 Run - Can't take log of 0
do not attempt to take log() of 0

github: fixes #21
2016-09-17 22:28:19 -04:00
Glenn Strauss
d7e46789a9 Run: employ $FindBin::Bin to find bin paths
github: fixes #14
2016-09-17 20:19:14 -04:00
Kelly Lucas
9665b29c99 Merge pull request #22 from meteorfox/fix-16-cpus-limitation
make maxCopies unbounded for 'system' and 'misc' suites
2016-09-17 15:51:53 -07:00
Chris Morgan
64c45b40c0 Fix for OS X based on https://gist.github.com/barusan/11033924
barusan's patch mostly retains compatibility with linux, but
unconditionally used machdep instead of /proc/cpuinfo

This attempts to merge the patch without harming behaviour on linux by
detecting the darwin platform and using machdep there but restores
/proc/cpuinfo elsewhere.
2016-03-24 15:48:15 -04: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
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