Skip to content
Snippets Groups Projects
Commit b4ac105d authored by Sebastian Thorarensen's avatar Sebastian Thorarensen
Browse files

Clarify that the benchmark directory must be empty before the benchmark

parent 81116a74
No related branches found
No related tags found
No related merge requests found
...@@ -36,7 +36,7 @@ where ...@@ -36,7 +36,7 @@ where
- <bytes per thread> is the number of bytes written and read per - <bytes per thread> is the number of bytes written and read per
thread (task), thread (task),
- <directory> is the path to a directory on the filesystem being - <directory> is the path to an empty directory on the filesystem being
benchmarked. benchmarked.
<threads per node> and <blocksize> will be chosen optimally for best <threads per node> and <blocksize> will be chosen optimally for best
...@@ -72,7 +72,7 @@ where ...@@ -72,7 +72,7 @@ where
- <bytes per thread> is the number of bytes written and read per - <bytes per thread> is the number of bytes written and read per
thread (task), thread (task),
- <directory> is the path to a directory on the filesystem being - <directory> is the path to an empty directory on the filesystem being
benchmarked. benchmarked.
<threads per node> will be chosen optimally for best performance. <threads per node> will be chosen optimally for best performance.
...@@ -107,7 +107,7 @@ where ...@@ -107,7 +107,7 @@ where
- <files per thread> is the number of files created, stat, and deleted - <files per thread> is the number of files created, stat, and deleted
per thread (task), per thread (task),
- <directory> is the path to a directory on the filesystem being - <directory> is the path to an empty directory on the filesystem being
benchmarked. benchmarked.
<threads per node> will be chosen optimally for best performance. <threads per node> will be chosen optimally for best performance.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment