Merge pull request #699 from lizwar/glibc-with-LSE

Glibc with lse_editorial review complete_KB to sign off

Author: pareenaverma

content/learning-paths/servers-and-cloud-computing/glibc-with-lse/_index.md

@@ -1,5 +1,5 @@
 ---
-title: Use glibc with Large System Extensions (LSE) to improve the performance of workloads on Arm servers
+title: Learn about glibc with Large System Extensions (LSE) for performance improvement
 
 minutes_to_complete: 60
 
@@ -12,6 +12,7 @@ learning_objectives:
 
 prerequisites:
 - An Arm based instance from a cloud service provider.
+- Review the learning path on [LSE](/learning-paths/servers-and-cloud-computing/lse/)
 
 author_primary: Ying Yu, Arm
 

content/learning-paths/servers-and-cloud-computing/glibc-with-lse/_review.md

@@ -13,7 +13,7 @@
 review:
     - questions:
         question: >
-            You can use LSE on Non-Arm servers?
+            Can you use LSE on Non-Arm servers?
         answers:
             - "Yes"
             - "No"

content/learning-paths/servers-and-cloud-computing/glibc-with-lse/build_glibc_with_lse.md

@@ -50,12 +50,12 @@ You have now successfully built glibc from source without LSE.
 
 Now lets look at how you can build it with LSE support.
 
-## Build glibc With LSE
+## Build glibc with LSE
 To build glibc with LSE, you should add `CFLAGS` and `CXXFLAGS` to the configure command.
 
-You can do this one of two ways. One way is to use "-mcpu=native" which tells the compiler to detect the architecture/micro-architecture of your machine. The other way is to pass the exact architecture option of your machine to the compiler using "-mcpu=neoverse-n2+lse"
+You can do this one of two ways. One way is to use "-mcpu=native" which tells the compiler to detect the architecture/micro-architecture of your machine. The other way is to pass the exact architecture option of your machine to the compiler using "-mcpu=neoverse-n2+lse".
 
-Both ways to configure are shown below:
+Both ways are shown below:
 
 ```bash
 sudo bash ~/glibc/configure --prefix=/usr --disable-werror CC=gcc-10 CXX=g++-10 CFLAGS="-mcpu=native -O3" CXXFLAGS="-mcpu=native -O3"

content/learning-paths/servers-and-cloud-computing/glibc-with-lse/compare_result.md

@@ -10,7 +10,7 @@ layout: "learningpathall"
 You can run the mongodb benchmark using Glibc with LSE and NoLSE and compare the results. This will give you an idea of the performance gained by using Glibc with LSE.
 
 ## Result with No-LSE
-Launch MongoDB with Glibc without LSE and obtain benchmark result.  
+Launch MongoDB with Glibc but without LSE and obtain a benchmark result.  
 The output will look similar to:
 
 ```output
@@ -62,7 +62,7 @@ The output will look similar to:
 The overall throughput (operations/sec) is 6662.1275371047195 with No-LSE Glibc.
 
 ## Result with LSE
-Launch MongoDB again, this time with Glibc with LSE and obtain benchmark result.
+Launch MongoDB again, this time with Glibc with LSE and obtain a benchmark result.
 
 The output will look similar to:
 
@@ -113,6 +113,6 @@ The output will look similar to:
 [SCAN], Return=OK, 1499682
 ```
 The overall throughput (operations/sec) is 6871.605426919102 when using Glibc with LSE.
-In this case you can get around 3.14% performance uplift by using Glibc with LSE.
+In this case, you get around 3.14% performance uplift by using Glibc with LSE.
 
 

content/learning-paths/servers-and-cloud-computing/glibc-with-lse/mongo_benchmark.md

@@ -96,7 +96,7 @@ You can now benchmark the performance of MongoDB following the `run` command:
 Replace `mongo_ip` and `mongo_port` in the command above with the IP address and port number of the machine you are running MongoDB on.
 
 {{% notice Note %}}
-Please ensure that you have sufficient disk space available! 
+Please ensure that you have sufficient disk space available (60GB as a minimum requirement).  
 {{% /notice %}}
 
 You can see the performance data after the `run` command execution is finished.

content/learning-paths/servers-and-cloud-computing/glibc-with-lse/mongo_start.md

@@ -46,16 +46,16 @@ logappend=true
 bind_ip=0.0.0.0
 port=27017
 ```
-You can now run MongoDB as shown:
+You can now run MongoDB as shown below:
 
 ```console
 cp /usr/lib/aarch64-linux-gnu/libcrypt.so ~/glibc-2.32_build_install/build/crypt/
 ~/glibc-2.32_build_install/build/testrun.sh ~/mongo/build/install/bin/mongod -f ~/mongodb-5.3.2/mongodb.conf --wiredTigerCacheSizeGB=20
 ```
 
-Confirm that the workload mongodb runs is with the newly built glibc with LSE:
+Confirm that the workload mongodb runs with the newly built glibc with LSE:
 
-First, get the pid with the following command.
+First, get the pid with the following command:
 ```console
 ps -ef | grep mongo
 ```