mdtest with fsync
 
 
 
 
Go to file
Wang Shilong 8902bc8722 mdtest: fix calculation for barriers
Currently, calculation for barriers case looks a bit
suprising, for example, Min stats is from min of
Max value of number of mpi proc, this makes Min
and Max very similar in our testing thus we get
a small Std value too.

I am not a MPI expert, but question is why we
don't use more nature calcuation which calculate
all results from different iterations and MPI proc?

Signed-off-by: Wang Shilong <wshilong@ddn.com>
2018-11-22 19:57:32 +08:00
config modernize configure 2017-10-19 15:18:39 -06:00
contrib Update cbif.c 2017-11-19 15:27:34 -06:00
doc Merge pull request #88 from roblatham00/hdf5-coll-md 2018-10-02 16:13:05 +01:00
src mdtest: fix calculation for barriers 2018-11-22 19:57:32 +08:00
testing fixes #87 2018-10-05 22:50:34 -07:00
.gitignore fix various issues related to release packages 2018-09-21 18:35:48 -04:00
.travis.yml fix various issues related to release packages 2018-09-21 18:35:48 -04:00
AUTHORS modernize configure 2017-10-19 15:18:39 -06:00
COPYRIGHT Numerous changes to file-modes, small build-tweaks, and a tweak to aiori-S3.c 2015-05-19 09:36:28 -06:00
META updated metadata for 3.2 2018-09-20 20:38:34 -04:00
Makefile.am fix various issues related to release packages 2018-09-21 18:35:48 -04:00
NEWS update known issues of 3.2.0 release 2018-10-06 09:31:53 -07:00
README.md Unit-test with automake for library version. Minor fix for library version. 2018-07-14 10:27:31 +01:00
README_S3 Numerous changes to file-modes, small build-tweaks, and a tweak to aiori-S3.c 2015-05-19 09:36:28 -06:00
bootstrap modernize configure 2017-10-19 15:18:39 -06:00
configure.ac compile correctly with -std=c99 2018-10-08 13:47:28 -07:00
travis-build.sh fix various issues related to release packages 2018-09-21 18:35:48 -04:00
travis-test.sh compile correctly with -std=c99 2018-10-08 13:47:28 -07:00

README.md

HPC IO Benchmark Repository Build Status

This repo now contains both IOR and mdtest. See also NOTES.txt

Building

  1. If "configure" is missing from the top level directory, you probably retrieved this code directly from the repository. Run "./bootstrap".

    If your versions of the autotools are not new enough to run this script, download and official tarball in which the configure script is already provided.

  2. Run "./configure"

    See "./configure --help" for configuration options.

  3. Run "make"

  4. Optionally, run "make install". The installation prefix can be changed as an option to the "configure" script.

Testing

Run "make check" to invoke the unit test framework of Automake.

  • To run basic functionality tests that we use for continuous integration, see ./testing/
  • There are docker scripts provided to test various distributions at once.
  • See ./testing/docker/