Skip to content

Commit 2d7deeb

Browse files
Update Redis learning path
1 parent 8402585 commit 2d7deeb

4 files changed

Lines changed: 59 additions & 47 deletions

File tree

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,25 @@
11
---
2-
title: Getting started with Redis on Google Axion C4A (Arm Neoverse-V2)
2+
title: Get started with Redis on Google Axion C4A
33

44
weight: 2
55

66
layout: "learningpathall"
77
---
88

9-
## Google Axion C4A Arm instances in Google Cloud
9+
## Explore Google Axion C4A Arm instances
1010

11-
Google Axion C4A is a family of Arm-based virtual machines built on Googles custom Axion CPU, which is based on Arm Neoverse-V2 cores. Designed for high-performance and energy-efficient computing, these virtual machines offer strong performance for modern cloud workloads such as CI/CD pipelines, microservices, media processing, and general-purpose applications.
11+
Google Axion C4A is a family of Arm-based virtual machines built on Google's custom Axion CPU, based on Arm Neoverse-V2 cores. These virtual machines deliver strong performance for modern cloud workloads such as CI/CD pipelines, microservices, media processing, and general-purpose applications.
1212

13-
The C4A series provides a cost-effective alternative to x86 virtual machines while leveraging the scalability and performance benefits of the Arm architecture in Google Cloud.
13+
The C4A series provides a cost-effective alternative to x86 virtual machines while leveraging the scalability and performance benefits of Arm architecture in Google Cloud.
1414

15-
To learn more about Google Axion, refer to the [Introducing Google Axion Processors, our new Arm-based CPUs](https://cloud.google.com/blog/products/compute/introducing-googles-new-arm-based-cpu) blog.
15+
Learn more about Google Axion from the Google blog [Introducing Google Axion Processors, our new Arm-based CPUs](https://cloud.google.com/blog/products/compute/introducing-googles-new-arm-based-cpu).
1616

17-
## Redis
17+
## Explore Redis
1818

19-
[Redis](https://redis.io/) is an open-source, **in-memory data structure store** developed under the [Redis project](https://redis.io/). It is used as a **database**, **cache**, and **message broker**, supporting a variety of data structures such as **strings**, **hashes**, **lists**, **sets**, and **sorted sets**.
19+
[Redis](https://redis.io/) is an open-source, in-memory data structure store developed under the [Redis project](https://redis.io/). It is used as a database, cache, and message broker, supporting a variety of data structures such as strings, hashes, lists, sets, and sorted sets.
2020

21-
Redis is designed for **high performance**, **low latency**, and **high throughput**, making it ideal for real-time applications. It supports **persistence**, **replication**, **Lua scripting**, **transactions**, and **high availability** through Redis Sentinel and **automatic partitioning** with Redis Cluster.
21+
Redis is designed for high performance, low latency, and high throughput, making it ideal for real-time applications. It supports persistence, replication, Lua scripting, transactions, and high availability through Redis Sentinel and automatic partitioning with Redis Cluster.
2222

23-
Redis is widely adopted for **caching**, **session management**, **real-time analytics**, **pub/sub messaging**, and **leaderboards** in gaming and web applications. It integrates seamlessly with programming languages like **Python**, **Java**, **Go**, and **Node.js**.
23+
Redis is widely adopted for caching, session management, real-time analytics, pub/sub messaging, and leaderboards in gaming and web applications. It integrates seamlessly with programming languages like Python, Java, Go, and Node.js.
2424

25-
To learn more, visit the [Redis official website](https://redis.io/) and explore the [documentation](https://redis.io/docs/latest/).
25+
To learn more, visit the [Redis website](https://redis.io/) and explore the [Reddis documentation](https://redis.io/docs/latest/).

content/learning-paths/servers-and-cloud-computing/redis-data-searching/baseline.md

Lines changed: 18 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,22 @@
11
---
2-
title: Redis Baseline Testing on Google Axion C4A Arm Virtual Machine
2+
title: Test Redis on Google Axion C4A
33
weight: 5
44

55
### FIXED, DO NOT MODIFY
66
layout: learningpathall
77
---
88

99
## Redis Baseline Testing on GCP SUSE VMs
10-
This section performs baseline testing for Redis running on a GCP SUSE Arm64 VM, focusing on data insertion, retrieval, and search performance.
10+
This section shows you how to perform baseline testing for Redis running on a GCP SUSE Arm64 VM, focusing on data insertion, retrieval, and search performance.
1111

1212
### Prerequisites
1313
This command launches the Redis server process in the background. It allows you to run subsequent commands in the same terminal session while Redis continues running.
14-
Start the Redis service in the background:
14+
Start the Redis service:
1515

1616
```console
1717
redis-server &
1818
```
19-
20-
**Check if Redis is active and responding to commands:**
21-
19+
Check if Redis is active and responding to commands:
2220
The redis-cli ping command sends a simple health check request to the Redis server. A PONG response confirms that the server is running correctly and the client can communicate with it.
2321
```console
2422
redis-cli ping
@@ -33,7 +31,7 @@ PONG
3331
### Insert Sample Data
3432
These steps populate the Redis database with a sample dataset to validate insertion performance and data persistence. You will create 10,000 key-value pairs using a simple shell loop and verify that the data has been successfully stored.
3533

36-
Use `redis-cli` to insert **10,000 sample key-value pairs**:
34+
Use `redis-cli` to insert 10,000 sample key-value pairs:
3735
```console
3836
for i in $(seq 1 10000); do
3937
redis-cli SET key:$i "value-$i" > /dev/null
@@ -59,6 +57,7 @@ Seeing `(integer) 10000` confirms that all key-value pairs were inserted success
5957

6058
Fetch one of the inserted keys to confirm data correctness:
6159

60+
Verify sample data retrieval:
6261
```console
6362
redis-cli GET key:5000
6463
```
@@ -74,8 +73,9 @@ You should see an output similar to:
7473
### Perform Basic Data Search Tests
7574
This step verifies Redis’s ability to retrieve specific data efficiently using unique keys. The `GET` command fetches the value associated with a given key from Redis.
7675

77-
You can test this by retrieving a known key-value pair:
76+
Verify Redis's ability to retrieve specific data efficiently using unique keys. The `GET` command fetches the value associated with a given key from Redis.
7877

78+
Test this by retrieving a known key-value pair:
7979
```console
8080
redis-cli GET key:1234
8181
```
@@ -112,8 +112,11 @@ You should see an output similar to:
112112
..........
113113
```
114114

115-
### Production-Safe Searching with SCAN
116-
This step introduces a production-friendly method for iterating through keys without blocking Redis operations.
115+
{{% notice Note %}}
116+
`KEYS` is fast but blocks the server when handling large datasets, so it's not recommended in production.
117+
{{% /notice %}}
118+
119+
### Production-safe searching with SCAN
117120

118121
Use the `SCAN` command for larger datasets — it is non-blocking and iterates safely.
119122

@@ -137,8 +140,11 @@ You should see an output similar to:
137140
Redis will return a cursor value (for example, `9792`).
138141
Continue scanning by reusing the cursor until it returns `0`, meaning the iteration is complete.
139142

140-
### Measure Data Retrieval Performance
141-
This step measures how quickly Redis can retrieve a single key from memory, helping to establish a baseline for data access latency on the Arm-based VM.
143+
### Measure data retrieval performance
144+
145+
146+
147+
Measure how quickly Redis can retrieve a single key from memory, helping to establish a baseline for data access latency on the Arm-based VM.
142148

143149
**Time Single Key Lookup**: Redis operations are extremely fast since data is stored in-memory. To quantify this, the Unix `time` command is used to measure the latency of retrieving a single key using `redis-cli`.
144150

content/learning-paths/servers-and-cloud-computing/redis-data-searching/installation.md

Lines changed: 22 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -7,31 +7,31 @@ layout: learningpathall
77
---
88

99
## Install Redis on GCP VM
10-
This section provides a complete guide to installing Redis on a **GCP SUSE virtual machine**. Redis will be built from source to ensure compatibility with the Arm architecture and to enable TLS support for secure connections.
10+
This section provides a complete guide to installing Redis on a GCP SUSE virtual machine. You will build Redis from source to ensure compatibility with the Arm architecture and to enable TLS support for secure connections.
1111

12-
### Prerequisites
13-
Before building Redis, update your package repositories and install essential build tools and libraries.
12+
## Prerequisites
13+
Before building Redis, update your package repositories and install essential build tools and libraries:
1414

1515
```console
1616
sudo zypper refresh
1717
sudo zypper install -y gcc gcc-c++ make tcl openssl-devel wget
1818
```
19-
### Download and Extract Redis Source Code
20-
This step downloads the Redis 8.2.2 source archive directly from the official GitHub repository, extracts the contents, and navigates into the extracted directory for compilation.
19+
## Download and extract Redis source code
20+
21+
Now download the Redis 8.2.2 source archive directly from the official GitHub repository, extract the contents, and navigate into the extracted directory for compilation:
2122

2223
```console
2324
wget https://github.com/redis/redis/archive/refs/tags/8.2.2.tar.gz
2425
tar -xvf 8.2.2.tar.gz
2526
cd redis-8.2.2
2627
```
2728
{{% notice Note %}}
28-
In [this](https://developer.arm.com/community/arm-community-blogs/b/servers-and-cloud-computing-blog/posts/improve-redis-performance-by-deploying-on-alibaba-cloud-yitian-710-instances) blog, Redis version 6.0.9 is recommended for deployment on Arm-based Alibaba Yitian 710 instances, which deliver up to 36% higher throughput and 20% lower cost compared to equivalent x86-based ECS instances, making it a more efficient and cost-effective choice for Redis workloads.
29+
In this blog [Improve Redis performance up to 36% by deploying on Alibaba Cloud Yitian 710 instances](https://developer.arm.com/community/arm-community-blogs/b/servers-and-cloud-computing-blog/posts/improve-redis-performance-by-deploying-on-alibaba-cloud-yitian-710-instances), Redis version 6.0.9 is recommended for deployment on Arm-based Alibaba Yitian 710 instances. These instances deliver up to 36% higher throughput and 20% lower cost compared to equivalent x86-based ECS instances, making it a more efficient and cost-effective choice for Redis workloads.
2930

3031
The [Arm Ecosystem Dashboard](https://developer.arm.com/ecosystem-dashboard/) recommends Redis version 6.0.9, the minimum recommended on the Arm platforms.
3132
{{% /notice %}}
3233

33-
### Build Redis with TLS Support
34-
**Clean any previous build artifacts (if any):**
34+
Clean any previous build artifacts (if any):
3535

3636
```console
3737
make distclean
@@ -48,9 +48,13 @@ sudo make hiredis jemalloc linenoise lua fast_float
4848
cd ..
4949
sudo make BUILD_TLS=yes
5050
```
51-
Note: The BUILD_TLS=yes flag enables TLS (SSL) support for secure Redis connections.
5251

53-
### Verify Redis Binary
52+
{{% notice Note %}}
53+
The `BUILD_TLS=yes` flag enables TLS (SSL) support for secure Redis connections.
54+
{{% /notice %}}
55+
56+
### Verify Redis binary
57+
5458
After a successful build, check that the redis-server binary exists:
5559

5660
```
@@ -65,28 +69,30 @@ You should see a file similar to:
6569
```
6670
This confirms that Redis compiled successfully and that the `redis-server` binary is present in the `/src` directory. The file’s permissions indicate it is executable.
6771

68-
### Install Redis System-Wide
69-
This command installs Redis binaries (`redis-server` and `redis-cli`) into system-wide directories (typically `/usr/local/bin`), allowing you to run Redis commands from any location.
70-
To make redis-server and redis-cli accessible globally:
72+
### Install Redis system-wide
73+
Use the following command to install Redis binaries (`redis-server` and `redis-cli`) globally, making them accessible from any directory:
7174

7275
```console
7376
sudo make install
7477
```
7578

79+
This places `redis-server` and `redis-cli` into `/usr/local/bin`, allowing you to run Redis commands from anywhere on your system.
80+
7681
Verify installation paths:
7782

7883
```console
7984
which redis-server
8085
which redis-cli
8186
```
8287

83-
Expected:
88+
The expected output is:
8489

8590
```output
8691
/usr/local/bin/redis-server
8792
/usr/local/bin/redis-cli
8893
```
89-
This confirms that Redis binaries are available in your system path, verifying a successful installation.
94+
95+
This confirms that Redis binaries are installed in your system path.
9096

9197
### Verify Installation
9298
Check Redis versions:
@@ -96,7 +102,7 @@ redis-server --version
96102
redis-cli --version
97103
```
98104

99-
Output:
105+
The expected output is:
100106

101107
```output
102108
redis-server --version

content/learning-paths/servers-and-cloud-computing/redis-data-searching/instance.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Create a Google Axion C4A Arm virtual machine on GCP
2+
title: Create a Compute Engine instance
33
weight: 3
44

55
### FIXED, DO NOT MODIFY
@@ -11,10 +11,10 @@ layout: learningpathall
1111
In this section, you will learn how to provision a Google Axion C4A Arm virtual machine on Google Cloud Platform (GCP) using the `c4a-standard-4` (4 vCPUs, 16 GB memory) machine type in the Google Cloud Console.
1212

1313
{{% notice Note %}}
14-
For support on GCP setup, see the Learning Path [Getting started with Google Cloud Platform](https://learn.arm.com/learning-paths/servers-and-cloud-computing/csp/google/).
14+
For support on GCP setup, see the Learning Path [Getting started with Google Cloud Platform](/learning-paths/servers-and-cloud-computing/csp/google/).
1515
{{% /notice %}}
1616

17-
## Provision a Google Axion C4A Arm VM in Google Cloud Console
17+
## Create your Google Axion C4A Arm VM
1818

1919
To create a virtual machine based on the C4A instance type:
2020
- Navigate to the [Google Cloud Console](https://console.cloud.google.com/).
@@ -28,16 +28,16 @@ To create a virtual machine based on the C4A instance type:
2828

2929

3030
- Under **OS and Storage**, select **Change**, then choose an Arm64-based OS image. For this Learning Path, use **SUSE Linux Enterprise Server**.
31-
- If using use **SUSE Linux Enterprise Server**. Select "Pay As You Go" for the license type.
32-
- Once appropriately selected, please Click **Select**.
31+
- If using **SUSE Linux Enterprise Server**, select **Pay As You Go** for the license type.
32+
- Once appropriately selected, select **Select**.
3333
- Under **Networking**, enable **Allow HTTP traffic**.
34-
- Click **Create** to launch the instance.
35-
- Once created, you should see a "SSH" option to the right in your list of VM instances. Click on this to launch a SSH shell into your VM instance:
34+
- Select **Create** to launch the instance.
35+
- Once created, you should see an **SSH** option to the right in your list of VM instances. Select this to launch an SSH shell into your VM instance:
3636

37-
![Invoke a SSH session via your browser alt-text#center](images/gcp-ssh.png "Invoke a SSH session into your running VM instance")
37+
![Google Cloud Console showing VM instances list with SSH button highlighted for connecting to the running C4A instance#center](images/gcp-ssh.png "SSH connection to VM instance")
3838

3939
- A window from your browser should come up and you should now see a shell into your VM instance:
4040

4141
![Terminal Shell in your VM instance alt-text#center](images/gcp-shell.png "Terminal shell in your VM instance")
4242

43-
Next, let's install redis!
43+
Next, install Redis.

0 commit comments

Comments
 (0)