Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
4d16acb2
Commit
4d16acb2
authored
Feb 01, 2019
by
Stan Hu
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Improve NFS benchmarking doc to include read performance test
parent
2d70977a
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
15 additions
and
4 deletions
+15
-4
doc/administration/operations/filesystem_benchmarking.md
doc/administration/operations/filesystem_benchmarking.md
+15
-4
No files found.
doc/administration/operations/filesystem_benchmarking.md
View file @
4d16acb2
...
...
@@ -9,11 +9,11 @@ Normally when talking about filesystem performance the biggest concern is
with Network Filesystems (NFS). However, even some local disks can have slow
IO. The information on this page can be used for either scenario.
##
Write Performance
##
Executing benchmarks
The following one-line command
is a quick benchmark for filesystem write
The following one-line command
s provide a quick benchmark for filesystem write and read
performance. This will write 1,000 small files to the directory in which it is
executed.
executed
, and then read the same 1,000 files
.
1.
Change into the root of the appropriate
[
repository storage path
](
../repository_storage_paths.md
)
.
...
...
@@ -27,13 +27,18 @@ executed.
```sh
time for i in {0..1000}; do echo 'test' > "test${i}.txt"; done
```
1.
To benchmark read performance, run the command:
```sh
time for i in {0..1000}; do cat "test${i}.txt" > /dev/null; done
```
1.
Remove the test files:
```
sh
cd
../
;
rm
-rf
test
```
The output of the
`time for ...`
command will look similar to the following. The
The output of the
`time for ...`
command
s
will look similar to the following. The
important metric is the
`real`
time.
```
sh
...
...
@@ -42,6 +47,12 @@ $ time for i in {0..1000}; do echo 'test' > "test${i}.txt"; done
real 0m0.116s
user 0m0.025s
sys 0m0.091s
$
time
for
i
in
{
0..1000
}
;
do
cat
"test
${
i
}
.txt"
>
/dev/null
;
done
real 0m3.118s
user 0m1.267s
sys 0m1.663s
```
From experience with multiple customers, this task should take under 10
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment