diff --git a/content/en/docs/Developerguide/figures/en-us_image_0260577785.png b/content/en/docs/Developerguide/figures/en-us_image_0260577785.png index 4a2ff4e441666446f154811420da438878011543..18e8adf66ed22260f482217fb06df381472fe626 100644 Binary files a/content/en/docs/Developerguide/figures/en-us_image_0260577785.png and b/content/en/docs/Developerguide/figures/en-us_image_0260577785.png differ diff --git a/content/en/docs/Developerguide/result-linear-scale-up.md b/content/en/docs/Developerguide/result-linear-scale-up.md index d4012a2479ec1e93bb4188ba7f54690d43c4f3e8..8af644c876da07cbc38295ec6421b1ffaca268d0 100644 --- a/content/en/docs/Developerguide/result-linear-scale-up.md +++ b/content/en/docs/Developerguide/result-linear-scale-up.md @@ -9,7 +9,7 @@ openGauss and MOT have been tested on the following many-core systems with excel Our TPC-C benchmark dated June 2020 tested an openGauss MOT database on a Taishan 2480 server. A 4-socket ARM/Kunpeng server, achieved throughput of 4.8 M tpmC. The following graph shows the near-linear nature of the results, meaning that it shows a significant increase in performance correlating to the increase of the quantity of cores **Figure 1** TPC-C on ARM \(256 Cores\)The following is an additional example that shows a test on an x86-based server also showing CPU utilization -![](figures/tpc-c-on-arm-(256-cores)the-following-is-an-additional-example-that-shows-a-test-on-an-x86-based-ser.png "tpc-c-on-arm-(256-cores)the-following-is-an-additional-example-that-shows-a-test-on-an-x86-based-ser") +![](figures/tpc-c-on-arm-(256-cores)the-following-is-an-additional-example-that-shows-a-test-on-an-x86-based-ser.png) **Figure 2** tpmC vs CPU Usage ![](figures/resource-utilization-performance-benchmarks.png "resource-utilization-performance-benchmarks")