joshuaboniface
/
blog
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fix wording issues in test examples

This commit is contained in:
Joshua Boniface 2023-07-31 15:09:07 -04:00
parent 94972f8b8c
commit a2c7fb5590
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
content/pvc-ceph-tuning-adventures-part-3.md
View File

@ -54,7 +54,7 @@ Due to an oversight, the primary PVC coordinator node actually flipped from node
## Test Outline and Hypothesis ## 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. * 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 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. 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. 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.