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
babaaba6
Commit
babaaba6
authored
Dec 13, 2018
by
Drew Blessing
Committed by
Achilleas Pipinellis
Dec 13, 2018
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update Filesystem Benchmarking to be more strict
parent
141e1b21
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
9 deletions
+7
-9
doc/administration/operations/filesystem_benchmarking.md
doc/administration/operations/filesystem_benchmarking.md
+7
-9
No files found.
doc/administration/operations/filesystem_benchmarking.md
View file @
babaaba6
...
...
@@ -44,12 +44,10 @@ user 0m0.025s
sys 0m0.091s
```
From experience with multiple customers, the following are ranges that indicate
whether your filesystem performance is satisfactory or less than ideal:
| Rating | Benchmark result |
|:----------|:------------------------|
| Best | Less than 10 seconds |
| OK | 10-18 seconds |
| Poor | 18-25 seconds |
| Very poor | Greater than 25 seconds |
From experience with multiple customers, this task should take under 10
seconds to indicate good filesystem performance.
NOTE:
**Note:**
This test is naive and only evaluates write performance. It's possible to
receive good results on this test but still have poor performance due to read
speed and various other factors.
\ No newline at end of file
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