Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
A
arrh-storage-benchmark
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Arrhenius upphandling lagring
arrh-storage-benchmark
Commits
b4ac105d
Commit
b4ac105d
authored
2 months ago
by
Sebastian Thorarensen
Browse files
Options
Downloads
Patches
Plain Diff
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
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README
+3
-3
3 additions, 3 deletions
README
with
3 additions
and
3 deletions
README
+
3
−
3
View file @
b4ac105d
...
@@ -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 a
n 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 a
n 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 a
n 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.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment