Update benchmarking.md

Author: pareenaverma

content/learning-paths/servers-and-cloud-computing/flink-on-gcp/benchmarking.md

@@ -8,44 +8,52 @@ layout: learningpathall
 
 
 ## Apache Flink Benchmarking
-This guide provides step-by-step instructions to set up and run **Apache Flink Benchmarks** on a **GCP SUSE VMs**. It covers cloning the repository, building the benchmarks, exploring the JAR, and listing available benchmarks.
+This section walks you through running Apache Flink microbenchmarks on a Google Cloud Axion C4A (Arm64) SUSE VM. You will clone the official Flink-benchmarks repository, build the benchmark suite, explore available tests, and run the Remote Channel Throughput Benchmark, one of the key indicators of Flink’s communication and data-transfer performance.
 
 ### Clone the Repository
-Start by cloning the official Flink benchmarks repository. This repository contains all the benchmark definitions and example jobs.
+Clone the official Flink microbenchmarks repository:
 
 ```console
 cd ~
 git clone https://github.com/apache/flink-benchmarks.git
 cd flink-benchmarks
 ```
+This repository contains microbenchmarks built using JMH (Java Microbenchmark Harness), widely used for JVM-level performance testing.
 
 ### Build the Benchmarks with Maven
-Use Maven to compile the benchmarks and generate the benchmark JAR. Skip tests to save time.
+Compile the benchmarks and create the executable JAR:
 
 ```console
 mvn clean package -DskipTests
 ```
-- **mvn clean package** → Cleans previous builds and packages the project.
+What this does:
+  * clean removes previous build artifacts
+  * package compiles the code and produces benchmark JARs
+  * -DskipTests speeds up the build since unit tests aren’t needed for benchmarking
+    
+After building, the compiled **benchmarks.jar** files appear under:
 
-After this step, the target directory will contain the compiled **benchmarks.jar**.
+```output
+flink-benchmarks/target/
+```
 
 ### Explore the JAR Contents
-Verify the generated files inside the `target` directory:
+Verify that benchmarks.jar was generated:
 
 ```console
 cd target
 ls
 ```
-You should see an output similar to:
+You should see:
 
 ```output
 benchmark-0.1.jar  classes            generated-test-sources  maven-status         protoc-plugins
 benchmarks.jar     generated-sources  maven-archiver          protoc-dependencies  test-classes
 ```
-- **benchmarks.jar**→ The main benchmark JAR file used to run Flink benchmarks.
+benchmarks.jar — Contains all Flink microbenchmarks packaged with JMH.
 
 ### List Available Benchmarks
-To view all the benchmarks included in the JAR:
+View all benchmarks included in the JAR:
 
 ```console
 java -jar benchmarks.jar -l
@@ -54,13 +62,15 @@ java -jar benchmarks.jar -l
 - This helps you identify which benchmarks you want to execute on your VM.
 
 ### Run Selected Benchmarks
-While the Flink benchmarking project includes multiple suites for state backends, windowing, checkpointing, and scheduler performance, this Learning path focuses on the Remote Channel Throughput benchmark to evaluate network and I/O performance.
+While the Flink benchmarking project includes multiple suites for state backends, windowing, checkpointing, and scheduler performance, in this Learning path you will run the Remote Channel Throughput benchmark to evaluate network and I/O performance.
+
+**Remote Channel Throughput**: This benchmark measures the data transfer rate between remote channels in Flink, helping to evaluate network and I/O performance.
 
-**Remote Channel Throughput**: Measures the data transfer rate between remote channels in Flink, helping to evaluate network and I/O performance.
+Run the benchmark:
 ```console
 java -jar benchmarks.jar org.apache.flink.benchmark.RemoteChannelThroughputBenchmark.remoteRebalance
 ```
-You should see an output similar to:
+You should see output similar to:
 ```output
 
 Result "org.apache.flink.benchmark.RemoteChannelThroughputBenchmark.remoteRebalance":
@@ -83,25 +93,16 @@ RemoteChannelThroughputBenchmark.remoteRebalance  DEBLOAT  thrpt   30  10536.511
 - **Min Throughput**: The lowest throughput was observed, and it shows worst-case performance.  
 - **Max Throughput**: Highest throughput observed, shows best-case performance.
 
-### Benchmark summary on x86_64
-To compare the benchmark results, the following results were collected by running the same benchmark on a `x86 - c4-standard-4` (4 vCPUs, 15 GB Memory) x86_64 VM in GCP, running SUSE:
-
-| Benchmark                                          | Mode     | Count | Score (ops/ms) | Error (±) | Min        | Max        | Stdev    | CI (99.9%)             | Units  |
-|---------------------------------------------------|---------|-------|----------------|-----------|------------|------------|---------|------------------------|--------|
-| RemoteChannelThroughputBenchmark.remoteRebalance | ALIGNED | 30    | 24873.046      | 892.673   | 11195.028  | 12425.761  | 421.057 | [11448.649, 12011.275] | ops/ms |
-| RemoteChannelThroughputBenchmark.remoteRebalance | DEBLOAT | 30    | 11729.962      | 281.313   | 11195.028  | 12425.761  | 421.057 | [11448.649, 12011.275] | ops/ms |
-
 ### Benchmark summary on Arm64
-Results from the earlier run on the `c4a-standard-4` (4 vCPU, 16 GB memory) Arm64 VM in GCP (SUSE):
+Results from the run on the `c4a-standard-4` (4 vCPU, 16 GB memory) Arm64 VM in GCP (SUSE) are summarized below:
 
 | Benchmark                                          | Mode     | Count | Score (ops/ms) | Error (±) | Min       | Max       | Stdev   | CI (99.9%)             | Units  |
 |---------------------------------------------------|---------|-------|----------------|-----------|-----------|-----------|---------|------------------------|--------|
 | RemoteChannelThroughputBenchmark.remoteRebalance | ALIGNED | 30    | 17445.341      | 153.256   | 10289.593 | 10687.736 | 89.987  | [10476.390, 10596.633] | ops/ms |
 | RemoteChannelThroughputBenchmark.remoteRebalance | DEBLOAT | 30    | 10536.511      | 60.121    | 10289.593 | 10687.736 | 89.987  | [10476.390, 10596.633] | ops/ms |
 
-### Apache Flink performance benchmarking comparison on Arm64 and x86_64
+### Apache Flink performance benchmarking observations on Arm64
 
-- The **ALIGNED mode** achieved an average throughput of **17,445 ops/ms**, demonstrating higher performance on the Arm64 VM.  
-- The **DEBLOAT mode** achieved an average throughput of **10,537 ops/ms**, slightly lower due to optimization differences.  
-- The benchmark confirms that the **Arm64 architecture** efficiently handles Flink's remote channel throughput workloads.  
-- Overall, the average throughput across both modes is approximately **14,854 ops/ms**, indicating strong baseline performance for Arm64 deployments.
+- Both the ALIGNED mode and DEBLOAT modes demonstrate a strong throughput on the Arm64 VM.  
+- The benchmark confirms that the Arm64 architecture efficiently handles Flink's remote channel throughput workloads.  
+- Overall, the average throughput across both modes is approximately **14,854 ops/ms**, indicating strong baseline performance for Arm64deployments.