Fix wording issues in test examples
This commit is contained in:
parent
94972f8b8c
commit
a2c7fb5590
|
@ -54,7 +54,7 @@ Due to an oversight, the primary PVC coordinator node actually flipped from node
|
|||
|
||||
## Test Outline and Hypothesis
|
||||
|
||||
This test used nearly the same test outline as the previous post, only with two additional test:
|
||||
This test used nearly the same test outline as the previous post, only with two additional tests:
|
||||
|
||||
* The first test is without any CPU limits, i.e. all cores can be used by all processes.
|
||||
|
||||
|
@ -64,13 +64,13 @@ This test used nearly the same test outline as the previous post, only with two
|
|||
|
||||
* The fourth test is with 3 total CPU cores dedicated to OSDs (3 "per" OSD).
|
||||
|
||||
* The fifth test is with 4 total CPU cores dedicated to OSDs (4 "per" OSD).
|
||||
* The fifth (new) test is with 4 total CPU cores dedicated to OSDs (4 "per" OSD).
|
||||
|
||||
* The sixth test is with 8 total CPU cores dedicated to OSDs (8 "per" OSD).
|
||||
* The sixth (new) test is with 8 total CPU cores dedicated to OSDs (8 "per" OSD).
|
||||
|
||||
Since there are half as many OSDs in these nodes (i.e. only 1 each), the OSD CPU count was scaled down to match the "per" numbers with the previous post.
|
||||
|
||||
The sixth test here was added due to an interesting observation in the results from the first 5 tests, specifically around random write performance, that will be discussed below.
|
||||
The fifth test was added for more details on the scaling between configurations, and the sixth was added later due to an interesting observation in the results from the first 5 tests, specifically around random write performance, that will be discussed below.
|
||||
|
||||
The results are still displayed as an average of 3 tests with each configuration, and include the 60-second post-test load average of all 3 nodes in addition to the raw test result to help identify trends in CPU utilization.
|
||||
|
||||
|
|
Loading…
Reference in New Issue