summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAchilleas Pipinellis <axil@gitlab.com>2018-12-13 19:15:25 +0000
committerAchilleas Pipinellis <axil@gitlab.com>2018-12-13 19:15:25 +0000
commiteb81c1239ef86561b4304339609be32318419dbb (patch)
treece00b37bb91303d9df4da4996c5a06c6316e7d29
parent141e1b2167ee9cc9b51e9becfde6c2e4f5bbae35 (diff)
parentbabaaba696f6ca512226788ab20117302f2af911 (diff)
downloadgitlab-ce-eb81c1239ef86561b4304339609be32318419dbb.tar.gz
Merge branch 'strict_fs_benchmarks' into 'master'
Update Filesystem Benchmarking to be more strict See merge request gitlab-org/gitlab-ce!23709
-rw-r--r--doc/administration/operations/filesystem_benchmarking.md16
1 files changed, 7 insertions, 9 deletions
diff --git a/doc/administration/operations/filesystem_benchmarking.md b/doc/administration/operations/filesystem_benchmarking.md
index 44018e966e0..0397452e650 100644
--- a/doc/administration/operations/filesystem_benchmarking.md
+++ b/doc/administration/operations/filesystem_benchmarking.md
@@ -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